Maintain Multi-Currency Revenue Reconciliation Controls

Required inputs

Have these details available before following the usage instructions.

• Reconciliation period, entities, currencies, accounts, materiality, and declared grain
• Transaction, billing, payment, settlement, bank, invoice, recognition, journal, ledger, and reporting extracts
• Exchange-rate source and dates, conversion, recognition, fee, tax, and close-cutoff policies
• Refund, chargeback, adjustment, and manual-journal evidence
• Prior exceptions and control results, finance and data owners, and external-reporting boundaries

How to use this Skill

When to use:
- A recurring close or control process must reconcile revenue across currencies and operational or accounting systems.
- Variances require a repeatable evidence classification and owner follow-up rather than an ad hoc explanation.

When not to use:
- Issuing accounting, tax, audit, or legal opinions.
- Posting journals, writing off balances, or approving external reporting.
- A single-currency check with no conversion, settlement, recognition, or system-boundary complexity.

Reusable method:
1. Freeze period, entities, currencies, accounts, materiality, policies, rate source, and reconciliation grain.
2. Map gross transactions through refunds, disputes, taxes, fees, settlements, FX, recognition adjustments, journals, and reported revenue.
3. Tie each stage to source evidence and preserve transaction, invoice, settlement, entity, currency, and period keys.
4. Classify each variance as timing, FX, policy, fee or tax, settlement, recognition, mapping, duplication, omission, data quality, manual journal, or unresolved.
5. Quantify only where evidence supports the bridge; state required inputs for every unquantified material item.
6. Assign each exception an owner, evidence request, materiality, due date, resolution state, and control consequence.
7. Record approved recurring controls for rate locking, cutoffs, duplicates, journal evidence, tie-outs, and exception aging.

Expected output:
A reusable reconciliation pack containing source-to-ledger map, bridge by currency and system, variance ledger, unresolved exceptions, policy questions, control results, remediation, owners, and finance-review dispositions.

Boundaries:
Do not invent rates, transactions, policy, postings, or sign-off. The data owner verifies extracts and lineage; the controller or finance owner approves policy interpretation, journals, close disposition, and external reporting; tax and audit reviewers decide matters within their remit. AMO-P-000251 is the grounding source.

Based on an Amo.ng Prompt

Multi-Currency Revenue Reconciliation Model

Open the linked Prompt to read the instructions this Skill is based on.

Completion criteria

Complete when:
- Material totals reconcile at the declared grain or the residual is quantified and owned.
- Every variance is evidenced, inferred, assumed, or unresolved and preserves its policy, rate, timing, and system boundary.
- Each unresolved exception has evidence needed, materiality, owner, due date, and next check.
- Required recurring controls have observable evidence for the period.
- The finance owner has an Accepted, Accepted with open exceptions, or Not ready close disposition.