How the Lockbox Import Process Works
The workflow typically starts when the bank makes a lockbox file or report available. The finance team retrieves the file and checks that it covers the intended deposit date and contains the expected payment records. The data is then prepared for the import method supported by the company's Sage 100 environment. Depending on the setup, this may involve a dedicated import function, a compatible utility, or an integration with the bank's service.
After import, receipt details are reviewed and matched to customer accounts and open invoices. Payments may settle one invoice, several invoices, or only part of an invoice balance. Once the records are validated, the receipts can be posted according to the organization's procedures. Finance staff should confirm that the total imported amount agrees with the bank's deposit information and that the resulting customer balances reflect the payments received.
Required Data and File Validation
Before importing, confirm that the bank's output matches the format expected by the selected Sage 100 import method. Important fields commonly include customer number, payment reference, check number, receipt date, deposit amount, invoice number, and remittance amount. Field names, date formats, decimal precision, and record structure must be interpreted consistently.
Validation should also identify missing customer references, duplicate payment identifiers, invalid dates, blank amounts, and invoice references that do not match open receivables. Keep a copy of the original bank file and record the import date, deposit batch, and any corrections made during review. These practices support traceability and help staff explain how imported receipts reached the general ledger and customer accounts.
Matching Receipts and Resolving Differences
Consider a bank lockbox file containing three customer payments: $1,250, $900, and $350. The total deposit is $2,500. If the bank report also shows $2,500, the deposit total agrees, but each receipt still needs to be matched to the correct customer and invoice records. If the $900 payment covers two invoices of $600 and $300, both invoices should be cleared when the payment is applied. If a payment cannot be identified, it should remain available for investigation rather than being assigned to an unrelated customer.
Imported records should be compared with bank totals and Sage 100 receipt batches. API Data Integration describes the exchange of information between systems through application programming interfaces, while API Bank Integration focuses on connections that exchange banking data with finance applications. These approaches may support more direct data exchange when the bank and accounting environment provide compatible interfaces.
ERP Integration and Automation Controls
For companies connecting bank data with Sage 100 and other finance systems, integrations should define how data is transferred, validated, and reconciled. The article ERP Integration Layer: How It Powers Finance Automation explains why the integration layer matters when finance workflows depend on timely ERP data. Similarly, ERP Modernization vs Finance Automation: Key Differences helps distinguish system upgrades from automating the work performed around an ERP.
Hyperbots Platform uses agentic AI to support finance and accounting tasks, including document processing and ERP integration. Its Company Specific Configurations can align workflows, roles, and general ledger structures with organizational requirements. Process Specific Capabilities are designed around individual finance workflows, while Ready to Deploy Capabilities provide pre-trained agents and ERP connectors for supported tasks. Where AI tools connect to accounting data, teams should also follow ERP Security Best Practices for Finance Teams (2026) to consider access controls, permissions, data exchange, and auditability. Retail businesses reviewing ERP requirements can consult ERP for Retail Industry: 2026 Guide to Platforms & AI for context on retail platforms and finance automation.
API Based AI Integration describes connecting AI capabilities with business applications through APIs, allowing information to move between systems according to defined permissions and workflows. Any such setup should preserve review controls for unmatched payments and maintain records of imported data and subsequent posting actions.
Best Practices for Accurate Imports
A consistent import routine helps keep customer accounts, deposit records, and financial reports aligned. Establish ownership for retrieving bank files, validating batches, resolving unmatched items, and approving final posting. Reconcile each imported batch promptly and retain evidence that supports the receipt totals and application decisions.
- Confirm the bank file date, format, record count, and deposit total before import.
- Check customer and invoice references against Sage 100 records.
- Review duplicate receipts, partial payments, and unidentified remittances before posting.
- Compare imported batch totals with bank deposit reports.
- Maintain an exception log and retain original files for audit support.
Summary
Sage 100 Lockbox Import brings bank-collected customer payment data into the accounting workflow for receipt recording and invoice application. Reliable results depend on compatible file formats, accurate customer and invoice matching, deposit reconciliation, and documented review controls. A standardized import process helps improve accounts receivable accuracy, cash visibility, and the quality of financial reporting.