A pending credit memo request should not reduce the source open balance as though an approved credit already exists. Preserve the issued invoice amount, isolate the requested amount as an unresolved exception, and lower or remove the affected collection-timing assumption until the request has a documented decision. This keeps accounting state and forecast judgment separate.
Oracle's receivables guidance describes dispute notes that retain a credit memo request number, dispute amount, reason, and internal comments. Oracle's credit memo request data model separately stores the approved credit memo identifier once a request is approved and the credit is created. That distinction is useful even when another accounting platform supplies the AR export.
Keep three states separate
Classify the invoice adjustment as one of these states:
- **Requested:** A customer or internal owner has requested a credit, but no approved source transaction exists.
- **Approved, not yet reflected:** Approval evidence exists, but the current AR snapshot has not yet incorporated the issued credit.
- **Issued and reflected:** The source export contains the credit or adjusted open balance and can be reconciled to the invoice.
Only the third state changes the validated source amount for the forecast. The first two states can change confidence, expected timing, and the action queue without silently editing the ledger fact.
Split the exposure when the request is partial
Record the full open invoice balance, requested credit amount, undisputed remainder, request date, reason, supporting source, owner, and next review date. If reliable evidence supports payment of the undisputed remainder, that portion may keep a separate collection range. Leave the requested portion unassigned unless a supported alternative exists.
The partial-dispute framework explains how to separate disputed line items from the remainder. The credit-memo aging check covers issued credits already present in the accounting source.
Define the invalidating events
For every timing assumption, state what would invalidate it:
- the request amount changes;
- the request is rejected;
- an approved credit posts;
- the invoice is corrected or reissued;
- the customer disputes a larger amount; or
- a receipt is applied before resolution.
When any event occurs, refresh the dated source and preserve the prior record rather than overwriting the history. Use the disputed-invoice forecast guide for the broader exception workflow and confidence labels for timing evidence.
Decision rule
A requested credit is evidence of uncertainty, not an issued adjustment. Keep the accounting balance unchanged until the source supports a new amount, while making the requested portion visible as an owned exception with no unsupported collection week.
AR Pulse analyzes an authorized QuickBooks receivables export, surfaces invoice exceptions, and produces a four-week collections range. It does not approve credits, modify books, interpret contracts, or promise payment. Finance teams needing a traceable review can apply for AR Pulse.