What happens when a transaction can't be coded automatically?
Short answer
It stays in a review queue and doesn't sync. A person assigns the GL code, often after getting a receipt or the business purpose behind the charge.
Automatic coding works from rules, vendor defaults, and past coding. When none of them points to one account, the transaction is held instead of guessed, so an uncertain code reaches a person before it reaches the ledger.
Common reasons a transaction isn't coded
- No rule and no history: A new vendor matches no coding rule and has no past coding to draw on.
- Unclear description: Bank lines like "POS 4471 SQ" or a payment processor name hide the actual merchant.
- Multi-purpose vendors: Marketplaces and wholesale clubs sell items that belong in many accounts.
- Unusual amount: A charge far larger than the vendor's history may be a capital purchase or a prepaid contract.
- Conflicting history: The same vendor was coded to different accounts in past periods.
- Missing dimension: The account is clear, but a required department, class, or project can't be inferred.
What happens next
- The transaction is held: It stays in a review queue and does not post or sync.
- The reviewer gathers context: A receipt, invoice, or memo, or a direct question to the cardholder or client.
- The reviewer codes it: The account and dimensions are set, with a note on why when the choice isn't obvious.
- The decision feeds forward: The code becomes history for the next similar transaction, and a vendor that recurs may justify a coding rule. New rules generally apply going forward; see whether coding rules apply retroactively.
Avoid parking items in suspense
Coding uncertain items to a suspense or "Uncategorized Expense" account to clear the queue moves the problem to close. If the period can't wait, use one clearing account, list every item in it, and clear it before the next close. A growing suspense balance is a common audit question.
What Ramp Stack does with an uncoded transaction
- Nothing syncs on its own: In Ramp Stack's Bank transactions workspace, a suggested code is only a proposal. The line stays in review until a person marks it ready.
- The agent asks: When an input or a judgment call is missing, a Stack agent asks a question instead of filling the gap.
- Clients can supply the missing piece: Firms can request a receipt or explanation through Client Portal, where clients respond through a secure link without a Ramp account.
- Corrections carry forward: The bookkeeper's final choice becomes part of the history Stack draws on for future suggestions.
Related questions
GL codes can differ for foreign and domestic charges to reflect variations in currency, tax rules, and entity structure. This distinction helps maintain accurate reporting and compliance across regions. Ramp automatically identifies the transaction’s country, currency, and entity, then applies the appropriate GL code and tax settings based on your accounting integrations.
Read moreYes. The vendor points to a likely account, the memo narrows it to the right one, and a reviewer confirms the suggested GL code before it syncs.
Read moreA single transaction can be split across multiple GL codes when it covers different departments, projects, or expense categories. This ensures each portion of the spend is recorded accurately and supports cleaner, more detailed financial reporting.
Read moreManagers usually cannot override accounting codes after month-end close to preserve data integrity. Any post-close adjustments must go through formal journal entries or finance approvals.
Read moreCoding rules typically apply only to new transactions after they are created. Past transactions may remain unchanged unless updated manually or through specific retroactive adjustments.
Read moreForeign-currency expenses are recorded in the merchant's currency, then translated into the entity's functional currency using the rate and date required by your accounting policy. Card transactions commonly use the cleared or posted amount because that is the final amount charged.
Read more