Step-by-Step Guide to Reconciling and Coding Commercial Card Transactions

Key Concepts You Need Before You Start

Before opening the module, it helps to understand a handful of terms that recur throughout US Bank Access Online. A transaction is a single posted charge or credit, identified by a merchant name, a posting date, an amount, and often a merchant category code. A cycle is the billing window, typically a calendar month, that groups transactions for statement and payment purposes. Coding is the act of tagging a transaction in US Bank Access Online with accounting values such as a cost center, general ledger account, project code, or tax indicator. Reconciliation is the confirmation step where you verify that a transaction is valid, supported by documentation, and correctly coded.

US Bank Access Online distinguishes between a cardholder view, which shows only the transactions on cards a person holds or manages, and an approver view, which surfaces the transactions a manager is responsible for signing off. Program administrators in US Bank Access Online see a broader set of controls, including the code lists, approval hierarchies, and export formats that shape how everyone below them works. Knowing which view you are in explains why two people looking at the same portal can see very different screens.

Two data concepts drive most of the automation in US Bank Access Online. The first is the merchant category code, a standardized number that classifies the type of business where a purchase was made. The second is Level II and Level III data, the enriched detail that some merchants transmit alongside a charge, such as tax amounts, line items, and unit quantities. When this data is present, US Bank Access Online can pre-populate coding fields and give you far richer information to reconcile against, which is why enriched transactions are usually faster to close.

Finally, understand the difference between default coding and applied coding. Default coding is the accounting string that US Bank Access Online assigns automatically based on the card, the cardholder, or a rule an administrator configured. Applied coding is what remains after you review, accept, or override those defaults in US Bank Access Online. A transaction can look fully coded on arrival, but reconciliation still requires you to confirm that the defaults are actually correct for that specific purchase.

The Transaction Lifecycle in Access Online

Every charge follows a predictable path through US Bank Access Online, and recognizing the stages makes the reconciliation work far less mysterious. A transaction begins when a merchant authorizes and then settles a charge. Once settled, it posts to your account and appears in the transaction management module of US Bank Access Online, usually within one to two business days. At this point it carries any default coding but has not yet been reviewed by a person.

From the posted state, a transaction moves into coding, where a cardholder confirms or edits its accounting fields and attaches supporting documentation. After coding, it enters review, where an approver examines the coded record against policy. Approved transactions are then locked and staged for export to the accounting system. If an approver rejects a transaction, US Bank Access Online returns it to the cardholder for correction before it can advance again. Understanding this back-and-forth is central to using US Bank Access Online efficiently, because a rejected item that sits untouched will stall the entire cycle close.

The table below shows a representative snapshot of the transaction grid as it appears in US Bank Access Online, with the status chips the portal uses to signal where each line stands.

Step-by-Step Coding and Reconciliation Workflow

The following sequence describes the core routine most cardholders perform in US Bank Access Online, usually once a week during the cycle and once more at cycle end. Working the list little and often in US Bank Access Online is far less painful than facing a full month of untouched charges the night before the close deadline.

Step one, open transaction management

Sign in to US Bank Access Online and open the Transaction Management area from the main navigation. Choose Transaction List to see charges for the current cycle. The list in US Bank Access Online defaults to your own cards; if you manage multiple cardholders, use the account selector to switch between them. Filter by status to isolate items that still need attention, since focusing on uncoded and pending lines keeps you from re-reviewing work that is already complete.

Step two, review each posted charge

Click into a transaction to open its detail view. US Bank Access Online shows the merchant name, posting and transaction dates, the amount, and any enriched Level II or Level III data the merchant provided. Compare these values against your own record of the purchase. If the amount, merchant, or date does not match what you expect, that is your first signal to investigate before coding anything in US Bank Access Online.

Step three, confirm or edit the coding

Move to the accounting section of the detail view. Here US Bank Access Online displays the default coding string and the editable fields your program uses, such as cost center, general ledger account, and project or tax indicators. Accept the default when it is correct, or select the proper value from the code lists your administrator maintains in US Bank Access Online. Where a single purchase belongs to more than one account, use the allocation feature to split the amount across multiple coding lines so the totals still reconcile to the original charge.

Step four, attach documentation and add a description

Add the business purpose and any required notes in the comment or description field, then attach the receipt or invoice if your program uses the receipt imaging capability in US Bank Access Online. A clear description now saves an approver from chasing you later and gives auditors the context they need without a separate email trail. Treat this step in US Bank Access Online as part of coding, not an optional extra.

Step five, save and mark reviewed

Save your changes. In most configurations US Bank Access Online lets a cardholder mark a transaction as reviewed, which signals to the approver that the line is ready. Saving without marking reviewed keeps the item in your queue, which is useful when you want to return to a charge you are still researching. Only mark reviewed in US Bank Access Online once you are confident the coding and documentation are complete.

Step six, approve or reject as an approver

If you hold an approver role, switch to your approval queue in US Bank Access Online. Examine each reviewed transaction for policy compliance, coding accuracy, and adequate documentation. Approve the ones that pass, and reject the ones that need work, always leaving a comment that tells the cardholder exactly what to fix. A rejected item in US Bank Access Online returns to the cardholder and must be corrected and re-reviewed before it can be approved.

Step seven, verify the cycle totals

Before the cycle closes, reconcile the whole set. In US Bank Access Online, confirm that the sum of your coded transactions matches the statement balance for the cycle, that every line has moved to approved, and that no items remain uncoded. Any difference between your coded total in US Bank Access Online and the statement figure points to a missing, duplicate, or disputed charge that must be resolved before close.

Coding Transactions to the General Ledger

Coding is where reconciliation meets accounting, and it is the step that most affects the quality of your financial reporting. The coding fields you see in US Bank Access Online are not generic; they are configured by your program administrator to mirror your organization's chart of accounts. A typical setup in US Bank Access Online includes a cost center that identifies the department bearing the expense, a general ledger account that classifies the type of expense, and one or more optional segments for projects, grants, or tax handling.

When a merchant sends enriched data, US Bank Access Online can use it to suggest coding automatically. A charge from a merchant whose category code maps to airfare, for example, may arrive in US Bank Access Online pre-coded to a travel account. Automation like this speeds the work, but it never removes your responsibility to confirm the result. A category code describes the type of merchant, not the business reason for a specific purchase, so a charge at an office supply store might belong to more than one account depending on what was actually bought.

Allocation is the tool for purchases that cross accounting boundaries. Suppose a single invoice covers software licenses for two departments. In US Bank Access Online you can split that transaction into two or more lines, assigning a distinct coding string and a portion of the amount to each. US Bank Access Online enforces that the split amounts sum exactly to the original charge, which keeps the reconciliation intact even when the accounting is complex. Percentage-based allocation is available in many configurations of US Bank Access Online for recurring splits that follow a fixed ratio.

Consistent coding pays off at export time. US Bank Access Online produces an accounting extract in the format your finance system expects, and clean, validated coding flows straight into your ledger without manual intervention. Sloppy coding, on the other hand, produces rejected records that someone must correct by hand, which erodes the efficiency the card program was meant to deliver. This is why administrators often build validation rules into US Bank Access Online that block invalid combinations of segments before a transaction can be approved.

Reconciliation Rules and Common Pitfalls

Reconciliation succeeds or fails on a simple principle: what you approve must equal what actually posted, supported by evidence. In US Bank Access Online, that means the coded and approved total for a cycle should tie exactly to the statement balance, every line should carry documentation appropriate to its amount, and every charge should reflect a legitimate business purpose. When those three conditions hold in US Bank Access Online, the cycle is genuinely reconciled rather than merely closed.

The most common pitfall is timing. A charge that authorized late in a cycle may not post until the next one, so a receipt in hand does not always mean a transaction is available to code yet. Wait for the charge to appear in US Bank Access Online rather than trying to force it, and match by posting date when you reconcile against the statement. A second frequent issue is the pending charge that never settles because the merchant reversed or reduced the authorization; in US Bank Access Online these should simply drop off and should not be coded.

Duplicate charges are another trap. Some merchants post a temporary authorization and a final settlement that briefly appear as two entries. In US Bank Access Online, wait until settlement is final before treating a pair of similar amounts as duplicates, and if a true duplicate persists it belongs in the dispute process, not in your coding. Partial refunds and credits should be coded in US Bank Access Online to the same account as the original purchase so the net effect lands correctly in your ledger.

Finally, watch the deadline. US Bank Access Online cycles close on a schedule, and once a transaction is locked for a closed cycle you generally cannot recode it without an administrator's help. Working your queue in US Bank Access Online steadily throughout the month, rather than in a single end-of-cycle push, is the single most reliable habit for clean reconciliation. It leaves time to resolve the odd discrepancy before the window shuts.

Handling Disputes and Adjustments

Not every charge that posts is valid. When you find an amount you do not recognize, a duplicate that truly settled twice, or a charge for goods you never received, US Bank Access Online provides a dispute workflow that runs alongside reconciliation. Initiating a dispute in US Bank Access Online flags the transaction and starts a formal review, and it is the correct path for anything you cannot resolve directly with the merchant.

Timeliness matters here, because card networks impose windows within which a dispute must be raised. Raise questionable items in US Bank Access Online promptly rather than waiting for cycle end, and keep coding the rest of your activity in the meantime so a single disputed charge does not hold up an otherwise clean reconciliation. A disputed transaction in US Bank Access Online should be noted clearly so an approver understands why it remains open.

Adjustments, credits, and chargebacks eventually flow back into US Bank Access Online as their own transactions. When a dispute resolves in your favor, a credit posts and must itself be reconciled and coded, typically against the same account as the original charge. Treating the credit in US Bank Access Online as a first-class transaction, rather than mentally netting it against the disputed charge, keeps your ledger and the statement in agreement.

Roles and How Their Responsibilities Compare

Reconciliation is a shared responsibility in US Bank Access Online, and the tasks divide clearly across three roles. The table below summarizes who does what during a typical cycle in US Bank Access Online so you can see where your work fits.

The clearest lesson from this division is that reconciliation quality begins with the cardholder. US Bank Access Online routes accurate, well documented coding through approval with almost no friction, while errors introduced at the coding stage cascade into rework for approvers and administrators alike. Approvers act as the control layer within US Bank Access Online, and administrators own the configuration that makes correct coding easy and incorrect coding hard. When all three roles use US Bank Access Online consistently, the monthly close becomes a formality rather than a fire drill.

How to Get Started With Reconciliation

If you are new to coding and reconciling in US Bank Access Online, the following short sequence will get you productive without needing to understand every advanced feature first.

1. Confirm your access. Verify that your US Bank Access Online login shows the cards you are responsible for, and ask your administrator to correct your role if you cannot see transactions you should in US Bank Access Online.
2. Learn your code lists. Ask which coding fields your program uses and what each value means, so that selecting the right cost center and account in US Bank Access Online is a quick decision rather than a guess.
3. Set a weekly rhythm. Block a short recurring time to work your transaction queue in US Bank Access Online, coding and documenting new charges before they accumulate.
4. Do a practice reconciliation. Before your first real cycle close, tie your coded total to the statement in US Bank Access Online so you learn where discrepancies come from while the stakes are low.
5. Confirm the deadline. Note your program's cycle close date in US Bank Access Online and build your routine to finish comfortably ahead of it, leaving room to resolve disputes.

Frequently Asked Questions

How long after a purchase does a transaction appear for coding?

A settled charge typically posts to US Bank Access Online within one to two business days. Until it settles it may show as a pending authorization, which cannot yet be coded. Wait for the charge to post in US Bank Access Online before attempting to reconcile it against your receipt.

What is the difference between marking a transaction reviewed and approving it?

Marking reviewed is a cardholder action in US Bank Access Online that signals the coding is complete and ready. Approving is an approver action in US Bank Access Online that accepts the transaction and advances it toward export. A reviewed item is not final until an approver approves it.

Can I split one charge across multiple accounts?

Yes. The allocation feature in US Bank Access Online lets you divide a single transaction into multiple coding lines by amount or percentage. The split amounts must sum to the original charge, which keeps your reconciliation exact even when the accounting is complex.

What should I do if my coded total does not match the statement?

Investigate rather than adjust. In US Bank Access Online, a mismatch usually means a missing charge, a duplicate, or an unresolved dispute. Locate the specific discrepancy and correct the underlying record in US Bank Access Online. Never edit an amount to force the totals to tie.

Can I fix coding after a cycle has closed?

Once a cycle closes and transactions lock in US Bank Access Online, cardholders generally cannot recode them. Corrections after close typically require an administrator or a journal adjustment in your accounting system, which is why finishing in US Bank Access Online before the deadline matters.

How do disputed charges affect reconciliation?

Raise the dispute in US Bank Access Online and note it clearly, then keep coding the rest of your activity. Any credit that results from the dispute posts to US Bank Access Online as its own transaction later and must be coded, usually to the same account as the original charge.

Where does my coded data go after approval?

Approved transactions are staged for an accounting extract that US Bank Access Online formats for your finance system. Clean coding flows into the general ledger automatically, while records with invalid coding are rejected by US Bank Access Online and must be corrected by hand.