SAP Business One Bank Statement Processing for Bookkeepers

SAP Business One bank statement processing takes a statement either as an electronic bank file, read through a format assigned to the house bank account, or as rows typed into the Bank Statement Details window. A PDF fits neither route. For a client whose bank sends only PDFs, convert each statement to checked rows first, then enter those rows.

What does SAP Business One bank statement processing expect?

SAP Business One bank statement processing expects three things before any statement arrives: the feature switched on for the company, a house bank account defined for each bank account you want to process, and a decision per account on whether statements are imported from a file or entered by hand. Everything after that depends on those settings.

SAP's own SAP Business One 9.0 course on bank statement processing setup walks through the setup in order. Bank statement processing is installed from the Basic Initialization tab of Company Details. Each house bank account then carries two fields that matter here: an Imported Bank Statement box and an Import File Name. With the box selected, statements for that account are expected to come in from a file in the chosen format. With it cleared, statements for that account are entered manually. The same course notes that an account set to import can still take a manually entered statement, and that imported statements can be edited afterwards.

The setup also covers bank operation codes and matching criteria. Operation codes translate the bank's own transaction codes into internal ones, such as a fee or an outgoing check, and each internal code carries a posting method. Matching criteria are the rules B1 uses later to propose which invoice, payment or journal entry a statement row belongs to. A bookkeeper who inherits a B1 company usually finds these already configured by the client's SAP partner, and it is worth reading them before the first statement goes in, because they decide what B1 will post on your behalf.

For a bookkeeper coming from QuickBooks or Xero, the key difference is that B1 treats the statement as a document. It has a header with the account, a statement date, a starting balance and an ending balance, and it has rows. B1 will not finalize it until the rows explain the gap between those two balances.

SAP B1 bank file formats and format projects

SAP B1 bank file formats are definitions that tell the import how to read one bank's electronic file. The Import from File button only reads files that match the format assigned to that house bank account. A format is backed by a bank format project file, with the extension .bfp, and system formats ship with one already assigned.

According to the setup course, valid formats exist for most countries where bank statement processing is offered, and SAP Business One partners can build new .bfp files with the Electronic File Manager add-on. You assign a format project to a file format by right-clicking its row in the File Format setup window. Only formats of the bank statement type appear in the house bank account's Import File Name list.

The SAP Business One 9.0 course on the bank statement processing working process shows what one of these files looks like. In its example, a text file from the bank has lines that each begin with a two-digit code. The first five lines and the last line feed the statement header. A line starting with 61 is a transaction, and a line starting with 86 adds detail to the transaction above it. Amounts carry a C for incoming money or a D for outgoing money.

Two practical points follow for a practice:

• Formats are per bank, not per client. Two clients at the same bank can share one format, while one client with accounts at three banks may need three.
• A new format is partner work. Building a .bfp file is a job for whoever supports the client's B1 installation. Ask before promising a client that their bank's file will import.

These courses were written for version 9.0, and menus can move between releases and localizations. Treat them as a map of the concepts and check the window names in the client's own installation.

Where do PDF statements stall in SAP Business One?

PDF statements stall in SAP Business One because the import reads structured bank files, not documents. A PDF is a picture of a statement laid out for a person to read. It has no line codes and no fixed fields, so no bank statement format can parse it, and the Import from File button has nothing it can use.

This is the gap a client falls into when their bank provides a PDF but no electronic statement file in a format their B1 installation can read. The client sends the PDF, the bookkeeper opens B1, and the only remaining route is the Create New button, which opens an empty Bank Statement Details window to fill by hand.

Typing a statement in from a PDF is slow and has the same weaknesses as any manual entry:

1. A line at the foot of a page gets skipped.
2. A wrapped description is entered as two rows.
3. A debit is keyed as a credit, which shows up only as a Difference that will not clear.
4. Dates near a year boundary are given the wrong year.

A converter removes most of that work. AutoBankConvert reads scanned and digital PDFs, checks that the opening balance plus the transactions equals the closing balance, and returns each statement as rows. Its homepage names QuickBooks and Xero files as its exports and says nothing about SAP Business One, so plan on using the checked rows as the source for B1 entry, not on a direct B1 import file.

If the client gathers several months of PDFs at once, the guide to downloading multiple bank statements at once covers getting a full run of months out of online banking in one sitting.

Entering converted statement rows in SAP B1 by hand

Entering converted statement rows in SAP B1 means opening the Bank Statement Details window for the house bank and keying each checked row, with the header balances taken from the converted statement. The conversion has already proved that the rows add up, so the typing becomes copying rather than reading a PDF line by line.

The steps below follow one statement from client PDF to a finalized B1 bank statement. The account, dates and amounts are an example.

1. Convert the client's PDF and confirm the balance check passed. If it failed, find the missing or misread line before going near B1.
2. In B1, open Bank Statement Processing from the Banking menu and choose the client's house bank in the Bank Statement Summary window.
3. Choose Create New to open the Bank Statement Details window.
4. Enter the statement date, the starting balance and the ending balance exactly as the converted header shows them.
5. Check that the default starting balance B1 offers equals the ending balance of the previous statement. A mismatch here means a statement is missing or was entered wrong.
6. Enter each row with its date, the internal operation code that fits it, and the amount in the incoming or outgoing column.
7. Fill the business partner name where the description names one. It helps B1 find matching documents.
8. Save as a draft if you will reconcile later.

Example rows ready for entry

The header for this example statement reads a starting balance of 18,000.00 and an ending balance of 20,515.00.

Typing is still typing, so keep the converted file open beside B1 and tick off each row. The guide to what lands in a bank statement review queue explains how lines that conversion was unsure about are held back, which is the right moment to resolve them, before they reach B1.

The SAP B1 Difference field and statement balances

The SAP B1 Difference field shows the starting balance plus all incoming amounts, minus all outgoing amounts, minus the ending balance. B1 will not finalize a bank statement until that figure is zero. A non-zero Difference means the rows do not explain the movement between the two balances.

Take the three-row June statement from the entry steps, with its starting balance of 18,000.00 and ending balance of 20,515.00: 18,000.00 plus 4,200.00 is 22,200.00. Subtract 1,650.00 and 35.00 and you reach 20,515.00. Subtract the ending balance of 20,515.00 and the Difference is zero.

The processes course lists three ways to clear a Difference: correct the starting or ending balance, change the existing rows, or add the rows that are missing. When the rows came from a statement that already passed a balance check, the cause is almost always one of these:

• A keying slip. Compare row totals between the converted file and B1. The row whose amount differs is the slip.
• A swapped direction. A fee entered as incoming produces a Difference of exactly twice the fee.
• A skipped row. The Difference equals the missing amount.
• A wrong starting balance. If the default B1 offered was overwritten, the Difference equals the size of that change.

That symmetry is useful. The converted statement and the B1 statement apply the same rule, opening balance plus movement equals closing balance, so a statement that passed one should pass the other unless something changed in between.

Matching converted rows to SAP B1 posting proposals

Matching in SAP B1 starts when you choose Posting Proposal for Uncleared Rows. B1 then searches existing invoices, payments and journal entries using the matching criteria set up for the account, and proposes candidates for each row. You clear the right proposal, reject the wrong ones, and finalize to post payments and reconcile the open items.

The processes course shows the behaviour in detail. When exactly one proposal fully matches a row, B1 selects both as cleared automatically. When several documents fit the criteria, such as three invoices of similar amount, B1 proposes them all and you choose which to clear. When nothing fits, you can open the row and add open documents or journal entries by hand.

Clean rows make this step faster in three ways:

• Consistent payee text lets you pick the right business partner on each row, which narrows the search.
• Reference numbers kept intact, such as an invoice number inside a deposit description, give the criteria something to match.
• Correct dates matter because B1 adds open documents with posting dates on or before the row's posting date.

Categorization in a converter and matching in B1 are different jobs. A converter suggests an account for a line; B1 links a row to a document that already exists. For lines with no document behind them, such as bank fees or card charges, the converter's suggested account tells you which operation code and offsetting account to use. The post on automatic transaction categorization with client rules covers how those suggestions are built, and the guide to the categorization confidence score explains which suggestions you can accept without a second look.

When SAP B1 statement processing is the wrong route for a client

SAP B1 statement processing is the wrong route when its setup and matching cost more than the statement is worth. A client with a dozen bank lines a month, no customer invoices in B1 and no SAP partner to maintain formats gains little from the full process. Plain journal entries from the converted rows may serve them better.

Signs that a simpler path fits:

• The client uses B1 mainly as a general ledger and rarely raises invoices in it, so posting proposals have nothing to find.
• The bank offers no electronic file and the client has no partner to build a format, so every statement would be keyed by hand anyway.
• The account is a credit card that the client treats as an expense list rather than a bank account to reconcile row by row.
• You are catching up a year of history, where entering twelve statements as documents takes far longer than posting totals and reconciling once.

None of that is a rule. It is a question to ask before committing hours to setup. If the client's B1 already has bank statement processing configured by a partner, use it, because the reconciliation history it keeps is worth having. If it does not, discuss the trade with the client and their partner first. Whichever route you choose, AutoBankConvert can take the PDF stage off your desk, so the time you spend in B1 goes on matching and review rather than reading statements.