How Small Suppliers Can Track Invoice Approvals and Payment Follow-Ups

01 · Diagnose the work behind the balance

An outstanding report answers only part of the question

An ageing report tells you how much is outstanding and how long it has been outstanding. For example, Zoho Books’ India receivables documentation lists an Invoice Details report with due dates and pending balances and an Aging Details report with transaction date, age, amount and balance due. Both can be exported.

That information is essential. But it does not necessarily explain why a specific customer has not paid.

The balance is identical. The second update tells the business what to do.

Keep the accounting record as the authority for the amount owed. Add an operational view for the work required to collect it. The two should support each other—not become competing versions of the accounts.

02 · Make each status actionable

Replace “payment pending” with a useful next action

Use a small set of internal work stages that your team can understand consistently. The following is a suggested operating model, not a mandatory sequence imposed by any accounting platform.

Suggested operating modelMove from a vague status to a verified next step

Do not mark an invoice “approved” because someone opened the email or said they would check it. Record how you know the status: a buyer email, a portal reference, a dated call note or another appropriate confirmation.

Also allow “status not confirmed.” It is better to show an information gap than turn an assumption into a green dashboard indicator.

Practical control flowSwipe sideways to follow all six control points

Original GreyBath educational diagram. The stages are a recommended operating model, not a universal buyer workflow or an accounting-system status map.

03 · Preserve the financial truth

Keep approval status separate from payment status

One status field cannot always describe the whole situation. An invoice may be approved but unpaid. It may be partly paid while the remaining amount is disputed. A buyer may report a transfer that your accounts team has not yet matched.

Use two separate views:

Financial position

Original invoice amount, payments received and matched, authorised adjustments and remaining balance.

Follow-up position

Current issue, supporting evidence, responsible person and next action.

Do not change the remaining balance merely to make it agree with a customer’s verbal claim. Have accounts verify and record the appropriate treatment.

Likewise, do not equate a buyer-network status with cleared funds. In SAP Business Network’s supplier view, Paid or Partially Paid for an invoice means the customer has paid or is in the process of issuing payment. Verify the bank credit and invoice allocation independently, and close the payment follow-up only after accounts has verified the receipt and any properly authorised remaining adjustments.

04 · Coordinate around one invoice record

Build one shared follow-up view

For a small business, the first version can be a controlled spreadsheet linked to documents and refreshed from the accounting system. You do not need to recreate the entire ledger.

Use an existing invoice identifier wherever possible. If invoices come from multiple company entities or systems, ensure the identifier remains unique across them.

Minimum useful recordKeep financial facts and collection work connected

Restrict financial edits to the appropriate accounts users. Other team members can contribute operational updates without independently changing the amount owed.

“One shared view” does not mean every employee needs access to every customer’s commercial information. Give each role the access its work requires.

One invoice, three questionsEach question is shown as a separate card

Question 1

What is owed?

1. Invoice amount
2. Payments received and matched
3. Remaining balance

Owned by Accounts

Question 2

What is happening?

1. Buyer confirmation
2. Missing document or issue
3. Evidence and last update

Verified, not assumed

Question 3

What happens next?

1. Named owner
2. Specific action
3. Next-action date

Assigned and tracked

Control rule: A payment promise is not cleared funds.

Original GreyBath educational diagram. It illustrates an operating model, not a live customer system or a claim that software controls the buyer’s approval process.

Keep three dates—not one

The agreed due date, buyer-promised date and next-action date serve different purposes. Suppose an invoice was due on 30 September. The buyer later promises payment on 8 October. Your team plans to confirm the transfer on 9 October. Keep all three dates.

Recording a later promise should not silently overwrite the original due date or erase the ageing history. Any formally agreed change to terms should be handled through the business’s authorised process.

This also prevents an operational problem: repeatedly moving a single date forward until an overdue invoice appears current.

05 · Resolve the actual dependency

Link the missing evidence to the invoice

Imagine a customer saying, “We cannot process this invoice because the receiving confirmation is missing.” The right response is not necessarily another copy of the invoice. It is to identify the required confirmation and get it to the right person.

This is a genuine dependency in some buyer systems. In a configured SAP Ariba goods-receipt-based invoice-verification workflow, an electronic invoice without an associated receipt can enter Awaiting Receipts when a reconciliation delay is configured. It can move on when a receipt is created, the delay expires or an invoice administrator starts reconciliation, so the exact dependency is configuration-specific.

For your own customers, establish what their process requires. A goods supplier might need a purchase-order reference, delivery acknowledgement or receiving confirmation. A service business might need completion or milestone acceptance. These are examples to verify with the customer—not a universal document list.

Keep the relevant files linked to the invoice record, with clear descriptions.

Avoid publishing invoice folders through unrestricted links. Share only what the intended recipient needs.

Give each issue one internal owner

“Accounts and sales are following up” sounds reassuring, but it can mean neither person knows who should act next. Assign one owner for the current action.

If a delivery document is missing, dispatch may need to provide it. If the price differs from the agreed order, sales may need to resolve it. If a transfer cannot be matched, accounts should investigate.

The person owning the customer relationship does not have to perform every task personally. They do need to know who is responsible.

That is enough to coordinate a small team without adding a complicated approval hierarchy.

06 · Ask for a specific decision

Change the message according to the issue

A standard “payment pending” message asks the customer to investigate the whole situation again. A specific message asks for a specific decision.

Before sending any message, check the latest accounts position and recent customer response. A correct message becomes incorrect if the customer paid after the tracker was last refreshed.

07 · Hypothetical operating example

The same ₹12.4 lakh, but a different action plan

Consider a fictional industrial-consumables distributor with 18 open invoices across six customers. Its accounting records show ₹12.4 lakh outstanding.

Previously, every invoice appeared in one list labelled “Payment follow-up.” The team reviews each invoice and groups it by its immediate next action:

Hypothetical exampleEach invoice is counted once by its main next action

Hypothetical balance breakdownSwipe sideways to compare every next-action group

Original GreyBath educational chart using the fictional figures in this article. It is not customer data, a recovery forecast or evidence of improved collection performance.

These figures are hypothetical. Each invoice is counted once by its main next action, and the amounts are remaining balances—not original invoice values.

The three invoices with commercial discrepancies do not necessarily have their entire ₹2,40,000 disputed. The team must establish the actual disputed amounts separately.

What changes immediately?

Dispatch now has four document tasks. Sales has three commercial issues to resolve. Accounts has five payment-date requests, two balance follow-ups and four status enquiries.

The owner can also see that ₹2.5 lakh has no confirmed operational explanation yet. That amount should not be presented as a confirmed near-term receipt merely because the invoices have been raised.

What has not changed?

The business is still owed ₹12.4 lakh. No payment has been recovered simply by creating the table.

The improvement is that the business now knows which actions to take. Actual collection must be measured separately when money is received and allocated. This is the difference between a useful operational system and a dashboard that only makes outstanding money look organised.

08 · Configure before commissioning

Use the features you already pay for

Before commissioning a new application, check the reporting, reminder and customisation features in your existing software.

For example, Zoho Books’ India receivables documentation lists an Invoice Details report with due dates and pending balances and an Aging Details report with transaction date, age, amount and balance due; both can be exported. That can supply the financial foundation for a follow-up view.

Its current reminder guidance documents customer invoice reminders based on due date and internal notifications based on an expected payment date. The “Don’t remind about payment until then” option suppresses regular customer reminders until that date. Availability and labels can vary by edition, country, configuration and permissions.

These examples are not a recommendation to change your accounting package.

Check your actual edition, configuration and access permissions before assuming a feature is available. The cheapest suitable solution may be better configuration—not new software.

09 · Automate verified rules

Automate internal actions before customer reminders

If your team cannot reliably identify the right next action, automatically sending more messages can create more confusion.

Begin with internal reminders. For example, notify the responsible employee when a document task is overdue, an expected buyer response has not arrived or an invoice has no assigned owner.

Then introduce customer reminders for situations where the information and message are dependable.

Build explicit exceptions into the process

Payment reported but not matched

Send the task to accounts rather than immediately sending another overdue notice.

Commercial dispute

Use a specific issue-resolution message rather than repeatedly demanding the full amount without context.

Buyer commitment still within the agreed follow-up window

Follow the defined schedule rather than sending unrelated reminders.

Financial data refresh failed

Hold affected automated messages until the balance is checked.

These are recommended operating controls. They need to be configured and tested; they should not be assumed to exist because an automation is switched on.

Your system cannot see a buyer’s approval process without a source

This is an important boundary. Your accounting system knows that you raised an invoice. It does not automatically know whether the customer’s purchase, warehouse or finance team has approved it.

Even established buyer networks depend on the information customers provide. SAP also says that not every customer sends remittance information to SAP Business Network. Treat a missing or stale network status as a reason to verify with the customer, not as proof of non-payment.

For each external status, identify the source:

• Buyer email or confirmation: Record who confirmed it and when.
• Buyer portal: Record the reference and last checked time.
• Supported integration: Record the source and synchronisation status.

If no supported connection exists, a controlled manual update may be the correct answer. Do not let software label a customer invoice “approved” merely because an internal employee approved sending it. Those are different approvals.

10 · Add software only for a proved gap

When a connected application becomes worthwhile

A shared tracker may remain sufficient when invoice volume is manageable, a small team owns the process and updates are easy to maintain.

Consider a connected workflow when the same information is being entered repeatedly, several teams need different permissions, documents are difficult to locate or management cannot tell which updates are current.

The starting scope should be narrow: import open invoices and balances, attach the relevant documents, assign follow-up owners, record buyer confirmations and show the next actions.

Keep the accounting system authoritative for financial records. Begin with read-only financial imports where that meets the need.

Before approving implementation, require tests for practical failure cases: a duplicate import, a partial payment, a customer dispute, a failed data refresh and an unauthorised user attempting to open another account’s documents.

Also agree who maintains the application and how the business can export its information. A new system should reduce manual coordination—not become another place staff must update after finishing their real work.

11 · Separate effort from results

Measure collection work and collection results separately

Use a few measures that answer different questions.

How much remains unexplained?

Track the number and balance of open invoices whose current position has not been confirmed. In the fictional example, four of 18 invoices fall into that category. That tells management where information is missing; it does not establish that those customers will fail to pay.

Are internal actions completed on time?

Track overdue document tasks, unresolved assignments and missed follow-up dates. This measures the part your team can directly control.

How long do confirmed approvals take?

For invoices with reliable submission and approval dates, examine the elapsed time. State whether you use calendar or working days and keep unapproved cases visible separately.

Do not calculate an apparently improving average by silently excluding invoices that remain stuck.

How much cash was actually received?

Use receipts matched by accounts. Do not count a buyer promise, an internal approval or a reduced balance caused by an authorised credit adjustment as cash collected.

Review these measures together. More activity is not automatically better collection, and better information is not itself a payment.

Know what this process cannot fix

An organised workflow cannot make an insolvent customer able to pay. It cannot decide a genuine contractual dispute, replace professional advice on legal recovery or correct the economics of an unprofitable order.

It can help your business distinguish those problems from missing documents, unclear responsibility and avoidable internal delays.

Keep tax adjustments, credit notes, formal changes to payment terms and legal escalation under the appropriate professional and management controls. The aim is not to automate every decision. It is to ensure that important invoices do not remain unexplained because the necessary information is scattered across people and systems.

The useful result: every invoice has a next action

Your business does not need another screen that says “₹12.4 lakh pending.” It needs to answer:

• Which invoices need a document?
• Which need a commercial decision?
• Which have confirmed approval?
• Which have a payment commitment?
• Who must act next?

Start with those questions using your existing records. Improve the process before adding automation. Once the rules are clear, technology can connect the information and make the work easier to manage.