Skip to main content
GullySystem
Other industries

Collections and Payment Follow-Up for Photography studios

Turn unpaid customer balances into assigned follow-up actions.

Sales and Distribution

Does this function belong in your operation?

Use when customer credit creates balances that require organised follow-up.

An invoice becomes due or a payment promise needs checking.

The advance, instalments and balance on delivery each carry a due date, and payments by cash, card, wallet or transfer get a receipt number.

Bring the records the workflow depends on.

  • Outstanding invoices
  • Customer contacts
  • Follow-up ownership and rules

Outputs to check

  • Assigned collection action list
  • Payment-promise and dispute history
  • Overdue balance follow-up report

Follow the collections and payment follow-up workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Prepare balances

    Use current invoices, credits and allocated receipts.

  2. 2. Prioritise action

    Assign due accounts and separate disputed amounts.

  3. 3. Contact the customer

    Record the discussion, promise and next date.

  4. 4. Check the outcome

    Confirm whether payment arrived or another decision is needed.

  5. 5. Close or escalate

    Remove settled items and route unresolved exposure to the authorised owner.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Accounts assistant

Works the list from the top and keeps the notes current.

Field collector

Carries the day’s route on a phone and records what was actually brought back.

Sales executive

Knows what the customer owes before asking for the next order.

Owner

Reads promises broken twice, and decides who stops getting goods.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Customer disputes invoice

Separate the dispute owner and action from routine payment reminders.

Promise date missed

Record the failed promise and route the next action under the agreed policy.

Payment received during follow-up

Reconcile it before sending another demand for the same amount.

Can this work independently?

Collections can use a reviewed outstanding-balance import. Invoice and receipt connections keep the amount current, while credit control decides whether further orders are held. Follow-up records do not post payments; settlement must come from the authorised receipt or accounting process.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Receipts management: Recorded customer payments and invoice allocations.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • WhatsApp and SMS: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • We go through your receivables and the way calls are made now. You send a recent outstanding statement. A note comes back on how accounts are grouped.
  • Timing before and after the due date, tone of messages and escalation limits are agreed. You approve the wording for each stage. Open bills are imported from your accounting software. The accounts team checks a sample against the ledger. Mismatches are corrected.
  • Collectors and the accounts assistant use the list beside their old method. Notes go in. Gaps in the list are fixed. Collectors are trained on the phone screens. The diary is set aside. From then on the daily list is the working tool.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Follow-ups use current balances.
  • Payment promises retain dates.
  • Settled invoices leave the active collection list.
Photography studios

How the business operates.

Wedding and portrait studios keep each booking, from advance to album delivery, in one shared record. Owners, photographers, album designers and hired cinematographers work on the same booking. It holds the date and advance, crew and call times, equipment issued, raw file handovers, the online selection, album stages and proofs, and the balance due on delivery. Each stage carries a promised date that you set.

Enquiries and packages

Record enquiries with dates, functions, budget and source, and packages with what each includes: hours, crew, spreads, prints and revisions.

Booking calendar

Show confirmed and tentative dates on one calendar, function by function, with a warning before a second booking is taken on a blocked date.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and packages. Record enquiries with dates, functions, budget and source, and packages with what each includes: hours, crew, spreads, prints and revisions.
  • Booking calendar. Show confirmed and tentative dates on one calendar, function by function, with a warning before a second booking is taken on a blocked date.
  • Advances and payment schedule. Track the advance, instalments and balance on delivery, each with a due date. Payments by cash, card, wallet or bank transfer carry a receipt number.
  • Crew assignment. Assign photographers, cinematographers, drone operators and assistants to each function with call time and venue. Double booking gets checked.

Operational bottlenecks to check

Dates can be promised twice

One booking is confirmed by call, another through social media. Both clients pay an advance. Then a crew is found at short notice.

Advances are not recorded against a name

A transfer arrives without a name against it. Months later, the client’s account of the amount cannot be checked.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry

    Record names, dates, venue, functions wanted, the package discussed and the source. A tentative hold can sit on the date. The family can decide meanwhile.

  2. 2. Date blocked against an advance

    Once the advance is received, the date is confirmed. The payment schedule goes on the booking. A second booking on a blocked date needs a deliberate override.

  3. 3. The shoot and the crew

    Assign the lead photographer, candid shooter, cinematographer, drone operator and assistants to each function with call times and venue. Camera bodies and lenses are issued against the shoot.

  4. 4. Raw files and selection

    Record the card handover, the file count and the disk it went to. A selection set goes to the client, and the chosen list returns to the studio on the booking.

  5. 5. Edit, proof and approval

    Editing and album design move through their own stages, each with a person and a promised date. Every revision is counted against what the package allowed.

  6. 6. Delivery and balance

    Record the album, prints, USB drive and gallery link as delivered on a date to a named person. Whatever is still due shows before handover.

Industry reports to connect with

  • Shoots booked by date, with the crew assigned to each
  • Advances received and balances still to collect, booking by booking
  • Jobs at each stage, from raw files through edit to album delivered
  • Albums past the date promised to the client

Questions before implementation.

When should photography studios consider collections and payment follow-up?

Use when customer credit creates balances that require organised follow-up. An invoice becomes due or a payment promise needs checking.

What should we bring to the requirements discussion?

Bring anonymised examples of Outstanding invoices; Customer contacts; Follow-up ownership and rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Turn unpaid customer balances into assigned follow-up actions. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Communication permissions and collection conduct remain your responsibility. The customer’s actual payment is recorded separately from follow-up activity.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Follow-ups use current balances. Use this check when reviewing the first working version.

Talk to us

Discuss collections and payment follow-up for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements