How to Execute the Monthly Accounting Closing in SAP Business One Step by Step - Featured Image

Publications

How to Run the Monthly Accounting Close in SAP Business One Step-by-Step

Hector Pincheira

Hector Pincheira

CIO | CTO
Digital Strategy & Technology Innovation

items

SAP Business One monthly accounting close: complete step-by-step guide

Every month-end brings the same challenge: closing the accounting period with no errors, no imbalances and no surprises. Yet many finance teams working with the SAP Business One monthly accounting close run it incompletely or out of order. As a result, they carry forward differences that pile up and blow up at the year-end close. In this tutorial, then, I give you a structured process with verification queries you can run in your company today.

SAP Business One monthly close - financial documents and calculator
An orderly monthly accounting close is the foundation of reliable financial statements

Why a structured monthly close makes the difference

The accounting close is not only a regulatory obligation. It is also the mechanism that guarantees your financial statements reflect the operating reality of the company. Without a clear checklist and verification queries, however, the process turns reactive: you correct errors instead of preventing them. A well-executed monthly close lets you catch inconsistencies while they are still manageable, not when the auditor finds them six months later.

First, a disciplined monthly close drastically reduces the effort of the annual close. Second, it produces timely financial information for decision making. For example, if you do not close a month properly, the next month's balance sheet is born with inherited errors. As a result, you build up accounting technical debt that grows exponentially.

Prerequisites

To run this process you need access to SAP Business One with financial administration permissions. You also need access to the Financials module, to Administration → Utilities and to Query Manager. So confirm with your administrator that your user holds the Financial Manager role or higher before you start. Then make sure every user has completed their transactions for the period before you begin the close.

Step 1: Check pending documents for the period

Before closing any period, you must make sure there are no draft or unposted documents. This query shows you exactly which documents could fall outside the close if you do not process them.

SQL Server

-- Documentos en borrador pendientes del período - SQL Server
SELECT
    'Factura Venta' AS [Tipo Documento],
    COUNT(*) AS [Cantidad],
    SUM(T0."DocTotal") AS [Monto Total]
FROM OINV T0
WHERE T0."DocStatus" = 'O'
  AND T0."DocDate" BETWEEN
      DATEADD(MONTH, DATEDIFF(MONTH, 0, GETDATE()), 0)
      AND GETDATE()
UNION ALL
SELECT
    'Factura Compra',
    COUNT(*),
    SUM(T0."DocTotal")
FROM OPCH T0
WHERE T0."DocStatus" = 'O'
  AND T0."DocDate" BETWEEN
      DATEADD(MONTH, DATEDIFF(MONTH, 0, GETDATE()), 0)
      AND GETDATE()
UNION ALL
SELECT
    'Entregas Pendientes',
    COUNT(*),
    SUM(T0."DocTotal")
FROM ODLN T0
WHERE T0."DocStatus" = 'O'
  AND T0."DocDate" BETWEEN
      DATEADD(MONTH, DATEDIFF(MONTH, 0, GETDATE()), 0)
      AND GETDATE()
UNION ALL
SELECT
    'Entradas Mercancía Pendientes',
    COUNT(*),
    SUM(T0."DocTotal")
FROM OPDN T0
WHERE T0."DocStatus" = 'O'
  AND T0."DocDate" BETWEEN
      DATEADD(MONTH, DATEDIFF(MONTH, 0, GETDATE()), 0)
      AND GETDATE()
ORDER BY [Tipo Documento]

SAP HANA

-- Documentos en borrador pendientes del período - SAP HANA
SELECT
    'Factura Venta' AS "Tipo Documento",
    COUNT(*) AS "Cantidad",
    SUM(T0."DocTotal") AS "Monto Total"
FROM "OINV" T0
WHERE T0."DocStatus" = 'O'
  AND T0."DocDate" BETWEEN
      ADD_MONTHS(LAST_DAY(ADD_MONTHS(CURRENT_DATE, -1)), 1)
      AND CURRENT_DATE
UNION ALL
SELECT
    'Factura Compra',
    COUNT(*),
    SUM(T0."DocTotal")
FROM "OPCH" T0
WHERE T0."DocStatus" = 'O'
  AND T0."DocDate" BETWEEN
      ADD_MONTHS(LAST_DAY(ADD_MONTHS(CURRENT_DATE, -1)), 1)
      AND CURRENT_DATE
UNION ALL
SELECT
    'Entregas Pendientes',
    COUNT(*),
    SUM(T0."DocTotal")
FROM "ODLN" T0
WHERE T0."DocStatus" = 'O'
  AND T0."DocDate" BETWEEN
      ADD_MONTHS(LAST_DAY(ADD_MONTHS(CURRENT_DATE, -1)), 1)
      AND CURRENT_DATE
UNION ALL
SELECT
    'Entradas Mercancía Pendientes',
    COUNT(*),
    SUM(T0."DocTotal")
FROM "OPDN" T0
WHERE T0."DocStatus" = 'O'
  AND T0."DocDate" BETWEEN
      ADD_MONTHS(LAST_DAY(ADD_MONTHS(CURRENT_DATE, -1)), 1)
      AND CURRENT_DATE
ORDER BY "Tipo Documento"

Note that in SQL Server we use DATEADD(MONTH, DATEDIFF(MONTH, 0, GETDATE()), 0) to get the first day of the current month. In SAP HANA, however, the logic is different: we use ADD_MONTHS(LAST_DAY(ADD_MONTHS(CURRENT_DATE, -1)), 1). That way, both versions correctly calculate the range of the current period.

Step 2: Run exchange rate differences

If your company handles transactions in multiple currencies, this step is critical. Unrealized exchange rate differences must also be posted before the close so that foreign currency balances reflect their real value. So you need to go to Financials → Utilities → Exchange Rate Differences and run the wizard, selecting the period close date.

Next, this query lets you check which accounts hold foreign currency balances that will generate adjustments:

SQL Server

-- Accounts with foreign currency balances - SQL Server
SELECT
    T0."AcctCode"      AS [Cuenta],
    T0."AcctName"      AS [Nombre],
    T0."ActCurr"       AS [Moneda],
    T1."Debit" - T1."Credit" AS [Saldo ML],
    T1."FCDebit" - T1."FCCredit" AS [Saldo ME],
    CASE
        WHEN (T1."FCDebit" - T1."FCCredit") <> 0
        THEN (T1."Debit" - T1."Credit") / (T1."FCDebit" - T1."FCCredit")
        ELSE 0
    END AS [TC Implícito]
FROM OACT T0
INNER JOIN JDT1 T1 ON T0."AcctCode" = T1."Account"
WHERE T0."ActCurr" <> ''
  AND T0."ActCurr" IS NOT NULL
  AND (T1."FCDebit" - T1."FCCredit") <> 0
  AND T1."RefDate" BETWEEN
      DATEADD(MONTH, DATEDIFF(MONTH, 0, GETDATE()), 0)
      AND GETDATE()
ORDER BY ABS(T1."Debit" - T1."Credit") DESC

SAP HANA

-- Accounts with foreign currency balances - SAP HANA
SELECT
    T0."AcctCode"      AS "Cuenta",
    T0."AcctName"      AS "Nombre",
    T0."ActCurr"       AS "Moneda",
    T1."Debit" - T1."Credit" AS "Saldo ML",
    T1."FCDebit" - T1."FCCredit" AS "Saldo ME",
    CASE
        WHEN (T1."FCDebit" - T1."FCCredit") <> 0
        THEN (T1."Debit" - T1."Credit") / (T1."FCDebit" - T1."FCCredit")
        ELSE 0
    END AS "TC Implícito"
FROM "OACT" T0
INNER JOIN "JDT1" T1 ON T0."AcctCode" = T1."Account"
WHERE T0."ActCurr" <> ''
  AND T0."ActCurr" IS NOT NULL
  AND (T1."FCDebit" - T1."FCCredit") <> 0
  AND T1."RefDate" BETWEEN
      ADD_MONTHS(LAST_DAY(ADD_MONTHS(CURRENT_DATE, -1)), 1)
      AND CURRENT_DATE
ORDER BY ABS(T1."Debit" - T1."Credit") DESC

Step 3: Verify that the ledger balances (debits = credits)

This is the most fundamental control of the close. Yet many teams skip it because they assume SAP never allows an out-of-balance entry. Manual adjustments, data imports or integration errors, however, can all create differences. So run this check before you close:

SAP Business One monthly close - balance verification
Verifying that debits and credits balance is the most critical control of the monthly close

SQL Server

-- Monthly balancing check - SQL Server
SELECT
    T2."PeriodName"    AS [Período],
    SUM(T1."Debit")    AS [Total Débitos],
    SUM(T1."Credit")   AS [Total Créditos],
    SUM(T1."Debit") - SUM(T1."Credit") AS [Diferencia],
    CASE
        WHEN ABS(SUM(T1."Debit") - SUM(T1."Credit")) < 0.01
        THEN 'CUADRADO'
        ELSE 'DESCUADRADO'
    END AS [Estado]
FROM OJDT T0
INNER JOIN JDT1 T1 ON T0."TransId" = T1."TransId"
INNER JOIN OFPR T2 ON T0."FinncPriod" = T2."AbsEntry"
WHERE T0."RefDate" BETWEEN
      DATEADD(MONTH, DATEDIFF(MONTH, 0, GETDATE()), 0)
      AND GETDATE()
GROUP BY T2."PeriodName"
ORDER BY T2."PeriodName"

SAP HANA

-- Monthly balancing check - SAP HANA
SELECT
    T2."PeriodName"    AS "Período",
    SUM(T1."Debit")    AS "Total Débitos",
    SUM(T1."Credit")   AS "Total Créditos",
    SUM(T1."Debit") - SUM(T1."Credit") AS "Diferencia",
    CASE
        WHEN ABS(SUM(T1."Debit") - SUM(T1."Credit")) < 0.01
        THEN 'CUADRADO'
        ELSE 'DESCUADRADO'
    END AS "Estado"
FROM "OJDT" T0
INNER JOIN "JDT1" T1 ON T0."TransId" = T1."TransId"
INNER JOIN "OFPR" T2 ON T0."FinncPriod" = T2."AbsEntry"
WHERE T0."RefDate" BETWEEN
      ADD_MONTHS(LAST_DAY(ADD_MONTHS(CURRENT_DATE, -1)), 1)
      AND CURRENT_DATE
GROUP BY T2."PeriodName"
ORDER BY T2."PeriodName"

If the result shows «DESCUADRADO», stop the close immediately. Then investigate the period's journal entries, filtering for those where debits and credits do not match at the individual transaction level.

Step 4: Reconciling balances with business partners

Next, verify that the customer and vendor balances in the general ledger match the balances in the business partner module. That is how you catch differences caused by manual adjustments or posting errors.

Navigate to Financials → G/L Account Balance Verification to run the native SAP Business One tool. If you need finer control, use the queries above filtered by the trade receivable and trade payable accounts. The result is a double check: the standard tool plus your own query.

Step 5: Change the period status

Once every check is complete, it is time to close the period. Navigate to Administration → System Initialization → Posting Periods. Locate the period you are closing and change its status from «Unlocked» to «Closing Period», or straight to «Locked», depending on your internal policy.

It is worth understanding the three available statuses. First, Unlocked allows every transaction without restriction. Second, Closing Period restricts postings to authorized users only, which is ideal while you finish the last adjustments. You can leave the period in closing status during the first days of the following month while you complete pending reconciliations. That way nobody else posts a transaction out of place while you wrap up the process.

Variations and use cases

The process described here adapts to different business scenarios. Here are the most common variations:

Multi-currency companies: add an extra step after step 2 to check the exchange rates stored in the ORTT table against the central bank's official rates. That guarantees your exchange rate difference adjustments use the correct rates.

Companies with multiple warehouses: before step 1, run a check that the accounting inventory value matches the value in the inventory module. That is how you catch differences between the general ledger and valued physical stock.

Progressive partial close: instead of closing everything at month end, move the submodules (purchasing, sales) to «Closing Period» as each one is completed. This cuts the workload on the last day and minimizes last-minute errors.

Best practices and common mistakes

Mistake 1: Closing without checking open documents. If you close the period with open deliveries or invoices, those documents end up in accounting limbo. The Step 1 query prevents this completely, so always run it first.

Mistake 2: Skipping exchange rate differences. Many companies skip this every month and only do it at year end. But piling up twelve months of exchange adjustments creates an enormous impact in a single period. Do it every month, no exceptions.

Mistake 3: Locking the period too early. If you lock before every adjustment is complete, you will have to unlock and close again. Use the «Closing Period» status as an intermediate step before the definitive lock.

Best practice: build a closing calendar with deadlines for each subprocess (sales closes on day 2, purchasing on day 3, finance on day 5). Then document the checklist as a query you can run as a close-status dashboard. That turns a chaotic process into a predictable, measurable one.

SAP Business One monthly close - financial verification process
A documented, repeatable monthly close is a sign of financial maturity

Official SAP resources

To complement this tutorial, the official SAP Business One documentation includes the guide Year-End Closing in SAP Business One which details the full year-end closing process with all its monthly prerequisites. The training module Handling Accounting in SAP Business One on SAP Learning covers posting period management with hands-on exercises. Together, these resources give you official backing to validate every step of the process you have just learned.

Conclusion

The monthly close in SAP Business One does not have to be a stressful, disorganized process. You now have a five-step process with verification queries for both SQL Server and SAP HANA that you can run straight from your Query Manager. Every month you will know exactly what to check, in what order, and how to spot problems before they turn into a crisis. The key, though, is not following the steps once: it is turning them into an operating habit for your finance team. Put this checklist to work from the next close and you will watch the quality of your financial information improve month after month.

Does your monthly close still feel like a race against the clock? As a member of the Círculo Estratégico you get access to exclusive tutorials like this one that turn chaotic processes into predictable flows. And if you need to adapt these queries to your own chart of accounts, share your case in the comments.

Most Read

QlikSense Hierarchy: parent-child chart of accounts expanded by levels
QlikSense Hierarchy: the Chart of Accounts That Doesn't Add Up
QlikSense Sum TOTAL: share of each family over the total
QlikSense Sum TOTAL: the Percentage That Changes When You Filter
SAP Business One Inventory Revaluation - featured image of the tutorial
SAP Business One Inventory Revaluation: Fix Wrongly Loaded Costs
Empty chamber with wooden benches: the counterweight that required being present to be used
The Veto You Had to Say in Person: Your Decisions With No Counterweight
SAP Business One customizations - featured image of the pre-upgrade audit tutorial
SAP Business One Customizations: Pre-Upgrade Audit
SAP Business One Customer Concentration - featured image of the tutorial
SAP Business One Customer Concentration: Measure Your Risk with SQL

RELATED ARTICLES