Credit card reconciliation is one of the most time-consuming tasks in any accounting department. Downloading statements, manually entering transactions, and cross-referencing GL entries adds up fast. For finance teams running NetSuite, there is a better way.

This post walks through a near-fully automated credit card reconciliation workflow that combines three components: QBO file downloads from the bank, Celigo integration flows, and NetSuite’s native Bank Feeds and Match Bank Data tools. The result is a streamlined, audit-ready process that dramatically reduces manual effort and eliminates the risk of duplicate entries.

Why Automate Credit Card Reconciliation?

Traditional credit card reconciliation requires an accountant to manually enter each transaction into the ERP, match it against a bank statement, and verify that every line is accounted for. With high-volume cards across multiple employees, recurring subscriptions, and travel expenses, this can mean hundreds of transactions per month entered by hand.

The automated approach outlined here eliminates manual data entry almost entirely. Instead:

• The bank produces a structured QBO file with every transaction.
• Celigo reads that file and automatically creates the corresponding GL records in NetSuite.
• Bank Feeds independently stream the bank’s actual transaction data into NetSuite.
• NetSuite’s reconciliation rules auto-match the two sides, leaving only exceptions for manual review.

The accounting team shifts from data entry to exception management — a far higher-value use of their time.

How the System Works: The Three-Layer Architecture

Before diving into the step-by-step process, it helps to understand how the three systems interact:

The critical insight here is that Celigo and Bank Feeds operate independently. Celigo handles GL creation. Bank Feeds handles statement ingestion. The Match Bank Data page is where these two streams meet and are reconciled.

The Step-by-Step Process

Here is a complete walkthrough of the automated reconciliation workflow, from bank portal to completed reconciliation in NetSuite.

Step 1: Download the QBO File from the Bank

Log into your bank portal, navigate to the credit card account, select your date range, and download transactions in QBO / QuickBooks format.

💡 You can safely download a QBO file covering any date range, including a full month or an overlapping period. Celigo tracks each transaction’s unique bank-assigned ID and will automatically skip anything it has already processed. There is no risk of creating duplicate GL entries.

Step 2: Upload the QBO File to the NetSuite File Cabinet

In NetSuite, navigate to Documents > Files > File Cabinet > Celigo and place the QBO file in the correct card-specific subfolder.

💡 No renaming required. Celigo identifies transactions by their internal IDs within the QBO file, not by the filename. Once processed, Celigo moves the file to a Backup folder automatically.

Step 3: Celigo Processes the File and Creates GL Transactions

Once Celigo detects the QBO file in the monitored folder, it reads each transaction and creates the appropriate NetSuite record automatically. The run schedule can be configured to match your team’s needs.

This is where the real power of the integration lives. Rather than manually entering each charge, Celigo reads the structured QBO data and creates properly coded GL records complete with amounts, dates, and memo fields sourced directly from the bank file.

Step 4: Bank Feeds Import All Bank Transactions

Running independently of Celigo, NetSuite Bank Feeds pulls in every transaction from the bank — purchases, refunds, rewards, and card payments — into the Match Bank Data workspace.

Bank Feed lines are not GL-impacting on their own. They exist purely as the bank’s official record of what occurred, serving as the reference point during reconciliation. Think of the left panel in Match Bank Data as your credit card statement and the right panel as your NetSuite books.

Step 5: Review the Misc. Vendor Saved Search

Before opening Match Bank Data, run the Misc. Vendors used on Credit Card Transaction Imports saved search and resolve any transactions flagged with a generic vendor assignment.

⚠️ This step must be completed before beginning reconciliation. When Celigo cannot match a merchant name to an existing NetSuite vendor, it assigns a Misc. Vendor placeholder. These transactions need their expense accounts corrected before the books are finalized.

Step 6: Reconcile in Match Bank Data

Navigate to Transactions > Bank > Match Bank Data. Select the card account and statement period. NetSuite’s reconciliation rules auto-match on memo, date, and amount. Review auto-matched pairs, manually pair any exceptions, then reconcile when the difference is $0.00.

Auto-Matching with Reconciliation Rules

NetSuite’s pre-configured reconciliation rules for each credit card account will automatically pair bank feed lines to Celigo GL transactions when three criteria align:

• Memo: The merchant description on the bank feed line matches the memo on the Celigo-created GL transaction.
• Date: The transaction date matches the posting date.
• Amount: The dollar amount matches exactly.

Click Run Reconciliation Rules to trigger the auto-matching process. Review all suggested pairs before confirming to ensure accuracy.

Manual Matching for Exceptions

Transactions where the memo, date, or amount differs slightly between the bank feed and the GL entry will not auto-match and require manual pairing. In the bank feed panel (left), locate the unmatched line; in the GL panel (right), find the corresponding Celigo transaction; check both; click Match.

⚠️ If a bank feed line has no corresponding GL transaction, the QBO file for that period may not yet have been uploaded, or Celigo may not have run since the upload. Allow time for Celigo to process the file after uploading, then refresh the Match Bank Data page.

Completing the Reconciliation

Once all bank feed lines are matched, confirm the difference shown at the bottom of the workspace is $0.00. Click Reconcile Account Statement, enter the Ending Statement Date and Ending Statement Balance, and click Reconcile.

Key Benefits of This Approach

What You Need to Implement This

Setting up this workflow requires configuration across all three systems. Here is what is involved:

Celigo Configuration

• A Celigo flow for each credit card account, configured to monitor a specific NetSuite File Cabinet folder.
• Flow logic to evaluate QBO transaction types and map them to Credit Card Transaction or Credit Card Refund records in NetSuite.
• Duplicate prevention logic using bank-assigned transaction IDs.
• Vendor and expense account mapping rules to reduce Misc. Vendor assignments.

NetSuite Configuration

• File Cabinet folder structure: one subfolder per card under a Celigo parent folder.
• Bank Feeds enabled and authenticated for each credit card account.
• Reconciliation rules configured in Match Bank Data for each card account (matching on memo + date + amount).
• A saved search to surface Misc. Vendor transactions for pre-reconciliation review.

💡 The initial configuration investment of setting up Celigo flows, File Cabinet folders, bank feeds, and reconciliation rules pays for itself within the first month for any company processing more than 50 to 100 credit card transactions per period.

How Stratos Can Help

Stratos ERP Partners specializes in NetSuite implementations, optimizations, and integrations including finance automation like this. This workflow is applicable across industries wherever businesses carry corporate credit cards: professional services, healthcare, nonprofits, distribution, retail and beyond. Any organization managing meaningful card volume in NetSuite can benefit from this approach.

Whether you are starting from scratch or looking to optimize an existing reconciliation process, we can help you configure Celigo flows, set up Bank Feeds and reconciliation rules, build exception-management saved searches, and get your team up and running quickly.

Ready to automate your credit card reconciliation? Contact Stratos ERP Partners to schedule a discovery conversation.

Quick Reference: End-to-End Process Summary