A new settlement code appeared: review its meaning before mapping it

Save the original settlement row, transaction identifier, description, currency and related order or case reference. Find any matching debit, credit or reversal. An unfamiliar positive amount may settle an earlier loss, while a negative amount may move funds between balances instead of representing a selling expense. The sign alone cannot determine the accounting account.

Stripe documents a reporting-category field that distinguishes events such as disputes, reversals and failed refunds more precisely than some transaction types. This illustrates why a broad label such as adjustment needs interpretation. Use the current primary documentation for the actual provider and the fields present in the business's export.

Ask what caused the transaction and what record already exists in the books. Locate the original sale, fee, reserve, claim or refund where applicable. A reversal may need to unwind an earlier entry, and a recovery may settle a receivable. Mapping every unfamiliar code to miscellaneous expense can make the payout reconcile while obscuring those relationships.

Give the accountant representative source rows and the provider's explanation. Record the approved classification, sign convention and whether the amount affects a customer, supplier or clearing balance. Preserve any conditions under which the same provider category requires different handling. A generic transaction description may contain several commercially distinct events.

If the provider's explanation remains unclear, retain the amount as an identified exception under the approved close policy. Do not invent a permanent mapping merely to make an import complete.

Apply the proposed mapping to a controlled sample that includes the original event and any reversal. Check the total effect on the provider balance, the resulting ledger account and the settlement-to-bank match. Include at least one negative and positive case where the category supports both. A rule that passes one payout may still mishandle the opposite sign.

For a hypothetical $75 recovery already recorded as a receivable, the settlement credit should clear that receivable under the approved process. Posting another $75 of income would duplicate the recovery. If no receivable exists, the accountant must determine the appropriate initial recognition from the actual facts. The same cash amount can require different entries because the prior record differs.

Record the rule's effective date, source definition, approving reviewer and connector configuration. Decide whether earlier unclassified rows need reprocessing and protect against importing them twice. Keep the original raw category in the ledger reference or supporting file so future reviewers can reconstruct the transformation.

Monitor newly encountered categories after connector or provider changes and compare the distribution of transaction types with prior periods. A sudden rise in a catch-all account may indicate that a new event bypassed review. Close the mapping task when the sample settlement reconciles, affected historical rows are resolved and the business knows who will assess the next unfamiliar code.