> ## Content Index
> Fetch the complete content index at: https://abundance.alloconomy.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# What Should Happen Next?
- URL: https://abundance.alloconomy.com/alloconomy/aging-what-should-happen-next/
- Published: 2026-11-14T17:22:06.000Z
- Updated: 2026-11-14T17:22:06.000Z
- Description: Follow settlement, supplier and refund cases to the evidence and person needed next.
- Author: Sathya Narayanan
- Tags: Alloconomy, Accounting, What Is Still Unfinished?, #series-detail, #Import 2026-11-14 09:13

Accounting · Three essays

## What Is Still Unfinished?

1. Part 1[Follow one transaction](https://abundance.alloconomy.com/alloconomy/what-is-still-unfinished/)Look inside a balance and connect an invoice to the payments and credits that resolve it.
2. Part 2[Build the aging report](https://abundance.alloconomy.com/alloconomy/aging-how-old-is-what-remains/)Choose a cutoff, age the unpaid remainders and reconcile the result to the books.
3. Part 3**Investigate the unfinished work**Current essayFollow settlement, supplier and refund cases to the evidence and person needed next.

*Maya, Mayan and the businesses are fictional. All amounts, dates and terms are invented teaching assumptions; factual background is publicly sourced. This fresh case carries no balances from earlier series.*

Maya sees a bank deposit smaller than the customer payments her bookshop recorded. Has money disappeared? Elsewhere, a customer says an approved refund has never arrived.

Both questions concern unfinished work. Neither is answered by checking whether an invoice is overdue.

## The smaller deposit

In a separate fictional batch, Stories Inc. has $10,000 of captured customer payments, $300 of processing fees and $700 of completed refunds. With no other movements, the expected payout is **$9,000**. These are invented amounts, not a provider’s rates; captured payments are not automatically recognized sales revenue.

Maya asks for the batch identifier, payment records, fee lines, refund records and bank payout reference. Together they explain the $1,000 difference. Stripe’s [payout-reconciliation report](https://docs.stripe.com/reports/payout-reconciliation?ref=abundance.alloconomy.com) illustrates this tracing for automatic payouts. Its [reporting guidance](https://support.stripe.com/questions/payout-reporting-options?ref=abundance.alloconomy.com) explains why manually chosen payouts do not necessarily have the same transaction-to-batch mapping.

If the expected $9,000 has not reached the bank, the next question concerns the payout’s status and expected arrival. The relevant clock follows settlement timing, not an invoice’s payment terms.

## The refund still waiting

In another simplified case, Maya has recognized a $120 obligation to refund a reader. Approval is recorded, but the case stays open until evidence supports its resolution. [AASB 15, paragraph 55](https://standards.aasb.gov.au/aasb-15-dec-2022?ref=abundance.alloconomy.com) provides one public accounting framework for refund liabilities; this case assumes the obligation has already been recognized.

A refund identifier and a pending status may indicate normal processing. A failure status needs action. An approval with no corresponding processor record may reveal a missed handoff or missing data; it does not, by itself, prove that nothing was sent. Stripe documents [pending and failed refunds and trace references](https://docs.stripe.com/refunds?ref=abundance.alloconomy.com), illustrating the evidence to investigate.

Maya assigns the case to customer support and payments operations. They establish what was submitted and what the customer received before deciding the next step. The obligation and provider-processing stage remain distinct.

## Five situations, different clocks

| Situation                     | Records that need linking                                                 | What remains outstanding                    | Appropriate aging clock                                  | Decision or investigation enabled                                                |
| ----------------------------- | ------------------------------------------------------------------------- | ------------------------------------------- | -------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Customer receivable           | Invoice, remittance, receipts, credits                                    | Unpaid invoice remainder                    | Days past due                                            | Mayan contacts the correct customer with the remaining claim supported.          |
| Supplier payable              | Supplier invoice, payment and application                                 | Unpaid or unapplied item                    | Due date; track unapplied payment separately             | Maya establishes whether money is still owed before considering another payment. |
| Payment settlement            | Customer payments, fees, refunds, payout, bank entry                      | Amount awaiting payout or explanation       | Since availability or expected payout date               | Reconcile the batch and investigate a missed arrival.                            |
| Goods received before invoice | Purchase order, receipt, supplier invoice                                 | Receipt/invoice difference                  | Since receipt; track invoice-first exceptions separately | Obtain the missing invoice or resolve quantity/price differences.                |
| Refund obligation             | Approval, original payment, refund identifier/status, completion evidence | Refund still owed or completion unconfirmed | Since obligation arose; separately since submission      | Distinguish processing time, failure and missing records.                        |

These are suggested clocks for these cases. Microsoft illustrates [supplier aging](https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/vendor-aging-report?ref=abundance.alloconomy.com). SAP illustrates [goods-receipt/invoice-receipt reconciliation](https://learning.sap.com/courses/invoice-verification-in-sap-s-4hana/using-fiori-apps-for-gr-ir-reconciliation?ref=abundance.alloconomy.com), often shortened to GR/IR: an account that connects receipt of goods with the supplier invoice. Clearing that stage does not establish supplier payment; [invoice verification and payment are separate stages](https://learning.sap.com/courses/explaining-payables-invoice-processing/exploring-the-procure-to-pay-process%5Fd7a4061e-3d6a-44ff-bab5-e548bc258dfc?ref=abundance.alloconomy.com).

![Three distinct investigations: $10,000 payments less $300 fees and $700 refunds explain a $9,000 payout; goods receipt and invoice clearing is separate from supplier payment; a refund approval needs completion evidence.](https://storage.ghost.io/c/f5/a9/f5a9f801-5a10-44d6-b07c-6658660be1a9/content/images/2026/11/what-is-still-unfinished/part-03-infographic-v2.png)

Choose the next evidence and the right clock. The centre panel follows Maya’s payable to supplier Mayan. The cases are separate; their amounts are not added together.

For Maya, matching Mayan’s machine invoice to the receipt of the machine checks whether delivery and billing agree. She must separately link her payable to the payments she made. Mayan traces the corresponding receivable in his own books.

## What linking enables—and what it cannot decide

Linked records let a team trace a balance to cases, find the oldest unresolved work, recognize partial settlement, assign follow-up and improve cash planning. Repeated missing remittances or failed handoffs become process questions.

With only a net balance, the items and their ages cannot be uniquely reconstructed: Part 1’s three histories all produce $9,000\. With detailed records, people can link them manually or in ordinary accounting software. A separately named matching engine is unnecessary. Automation can make repeated work practical at scale; it cannot supply missing evidence.

Linking items within an account and comparing records across systems are both reconciliation techniques. Oracle explicitly describes [both approaches](https://docs.oracle.com/en/cloud/saas/account-reconcile-cloud/raarc/admin%5Ftrans%5Fmatch%5Freconcilation%5Fmethods%5Fabout.html?ref=abundance.alloconomy.com). Product documentation illustrates implementations, not universal accounting requirements.

Our examples also show the limits. Two unrelated errors can offset to zero. Incorrect references can create false matches. Missing records can leave a neat report incomplete. Open items can reflect normal timing, and age alone proves neither fraud nor uncollectability. Matching does not collect cash, complete a refund, establish revenue recognition or authorize a write-off. Nor should every balance-sheet asset, liability or equity balance clear to zero.

Choose one relevant balance. Ask for the oldest cases, supporting records, responsible person and next action. An investor can ask what explains changes in overdue receivables, settlement delays and working capital, while recognizing that detailed aging schedules may be internal and absent from published statements.

**If a payroll-clearing balance remained open after payday, which records and clock would you choose before deciding that employees had not been paid?**

---

[← Previous: How Old Is What Remains?](https://abundance.alloconomy.com/alloconomy/aging-how-old-is-what-remains/)