Process bank transactions

This field displays the matching status for the transaction. See Matching type for additional information related to each level.

Transactions can have one of four initial matching levels:

A: An exact match to one or several open items (or a general ledger account) was found.

AC: An exact match to an open item in currency

AP: An exact match to an existing payment

AM: A manual match to an open item or payment

AS: The transaction was automatically assigned to a general ledger account or a BP or an existing payment according to search terms defined in the search term list function.

B: Some information was found, but not an exact match. Possible matching open items and/or existing payment are displayed.

BC: Some information was found for entries in currency, but not an exact match. Possible matching open items and/or existing payment are displayed.

BP: Some information was found, but not an exact match. Possible matching open items and/or existing payment are displayed.

C: No matches were found and there are no possible matches.

This field indicates whether the match refers to an open item, existing payment, or a manual entry. For B and C match levels, this field is empty.

O: a match for an open item

P: a match for an existing payment

M: manual entry

Matched: Transaction is matched but not validated. It is possible to modify the matching.

Validated: Transaction is validated. You can no longer make modifications.

Partially validated: The transaction is assigned to two more open items where at least one open item is settled outside the bank transaction management, e.g., accidentally between matching and validating the bank statement. You cannot validate the statement. An error message displays in the log file and no payment is generated. The payment status for the transaction is set to Partially validated because Enterprise Management cannot validate all open items.

Manually completed: Indicates a transaction that has been manually processed or closed.

This field displays the payment number generated for validated transactions with a C matching flag.

Payment numbers for A and AM matches display in the Open item grid for the relevant open item.

Payment numbers for AS and AD matches display in the Manual entry Action according to the assigned general ledger or BP account.

Matching to existing payments does not generate new payments.

This field displays the value date in the bank statement transaction. This date determines the accounting date for the payment (s) created for this transaction.

This field indicates whether the transaction amount is a Revenue (credit) or an Expense (debit).

A bank sign C (credit) in MT940 or CRDT (credit) in CAMT.053/.054 represents payments received and displays as Revenue.

A bank sign D (debit) in MT940 or DBIT (debit) in CAMT.053/.054 represents payments issued and displays as Expense.

This field displays an overview of matching information at-a-glance. It displays the document number of matched items and/or the text “manual entry” if manual entries exist for the transaction. The display is limited to 250 characters.

Select this option to view to the original document.

Select this option to view the account for the open item on the line.

Select this option to view payment details for the open item on the line.

Select this option to view business partner details.

The fields in the Open items grid display information for possible transactions that result from an automatic match or manual match search. Only the Paid column field can be modified when you select the open item.

The fields in the Open items grid display information for possible transactions that result from an automatic match or manual match search. Only the Paid column field can be modified when you select the open item.

The fields in the Open items grid display information for possible transactions that result from an automatic match or manual match search. Only the Paid column field can be modified when you select the open item.

The fields in the Open items grid display information for possible transactions that result from an automatic match or manual match search. Only the Paid column field can be modified when you select the open item.

The fields in the Open items grid display information for possible transactions that result from an automatic match or manual match search. Only the Paid column field can be modified when you select the open item.

The fields in the Open items grid display information for possible transactions that result from an automatic match or manual match search. Only the Paid column field can be modified when you select the open item.

The fields in the Open items grid display information for possible transactions that result from an automatic match or manual match search. Only the Paid column field can be modified when you select the open item.

The fields in the Payments grid display information for possible transactions that result from an automatic match or manual match search. You cannot modify the amount for a matched payment.

The fields in the Payments grid display information for possible transactions that result from an automatic match or manual match search. You cannot modify the amount for a matched payment.

The fields in the Payments grid display information for possible transactions that result from an automatic match or manual match search. You cannot modify the amount for a matched payment.

The fields in the Payments grid display information for possible transactions that result from an automatic match or manual match search. You cannot modify the amount for a matched payment.

The fields in the Payments grid display information for possible transactions that result from an automatic match or manual match search. You cannot modify the amount for a matched payment.

This field displays the total assigned amount for open items selected in the grid.

This field only displays if open items are selected.

This field displays the total discount, if any, for selected open items.

This field display any remaining amount not yet assigned to open items or existing payments. It is calculated on the difference between the bank statement transaction amount minus the total of all assigned amounts.

Enter an amount to create an overpayment. This field is only available if open items have been selected. Overpayment is used when the bank transaction amount is higher than the total amount of selected open items. For example, a customer has accidentally paid too much.

This field displays the total manual entry amount entered for the bank statement transaction. To enter or modify an amount, use the Manual entry action.

This field displays the sub-detail amount in the transaction currency.

This sub-detail only represents CAMT.053/.054 transactions. It does not apply to other formats.

This field displays the sub-detail entry in the transaction currency.

This sub-detail only represents CAMT.053/.054 transactions. It does not apply to other formats.

This field indicates whether the sub-detail entry is credit or debit.

For camt.053/.054 transactions, a C (CRDT) bank sign represents payments received. A D (debit) bank sign represents payments issued.

This sub-detail only represents CAMT.053/.054 transactions. It does not apply to other formats.

This field displays bank account information related to the sub-detail entry, such as an IBAN.

This sub-detail only represents CAMT.053/.054 transactions. It does not apply to other formats.

This field provides BP information included in the sub-detail transaction such as the related debtor or creditor.

This sub-detail only represents CAMT.053/.054 transactions. It does not apply to other formats.

This field displays the structured or unstructured information that enables matching a sub-detail entry to an open item such as invoice numbers, End-to-End identification, etc.

This sub-detail only represents CAMT.053/.054 transactions. It does not apply to other formats.

This field displays the structured bank transaction codes included in a sub-detail transaction entry.

The field value for transaction code 1 represents the Domain code.

The field value for transaction code 2 represents the Family code.

The field value for transaction code 3 represents the Sub-family code.

Bank transaction codes represent a harmonized ISO20022 code set that helps to fully identify the type of underlying transaction and assigns it to a general ledger account or a BP based on the search term list function.

This sub-detail only represents CAMT.053/.054 transactions. It does not apply to other formats.

This field displays the ISR reference number, if applicable, included in the sub-detail transaction entry.

This sub-detail only represents CAMT.053/.054 transactions. It does not apply to other formats.

These fields display search criteria selected in the Bank import settings function (BSIIMPPAR) and which data types matched those criteria. It also displays the control for the Use search term list. These fields cannot be modified.

These fields display search criteria selected in the Bank import settings function (BSIIMPPAR) and which data types matched those criteria. It also displays the control for the Use search term list. These fields cannot be modified.

These fields display search criteria selected in the Bank import settings function (BSIIMPPAR) and which data types matched those criteria. It also displays the control for the Use search term list. These fields cannot be modified.

These fields display search criteria selected in the Bank import settings function (BSIIMPPAR) and which data types matched those criteria. It also displays the control for the Use search term list. These fields cannot be modified.

These fields display search criteria selected in the Bank import settings function (BSIIMPPAR) and which data types matched those criteria. It also displays the control for the Use search term list. These fields cannot be modified.

These fields display search criteria selected in the Bank import settings function (BSIIMPPAR) and which data types matched those criteria. It also displays the control for the Use search term list. These fields cannot be modified.

Select this action to validate the current statement according to the rules below:

For A level matches

• To open items: This generates the payment and no more changes can be made.
• To existing payments: This simply creates the match to the bank transaction with no new posting or payments.*
• To an existing payment linked to a manual entry: This matches the existing payment and creates a new payment posting for the manual entry amount only.

*For A level matches to existing payments, validation creates the following data:

PAYMENTH: a reference to the linked transaction in BSIIMPD

GACCENTRY: creates a matching flag entry (value BSI) for those journal entries related to the entry in PAYMENTH

Select this action to start the automatic matching for the current bank statement transaction only. To start the automatic matching for the entire statement at once, use the Match statement action.

Select Manual entry to post transactions for B or C matches to a general ledger or BP account without assigning them to an open item, i.e., payment to an account. You can distribute the payment to multiple accounts, but you cannot change the total payment amount because the complete transaction amount must be distributed. If you create multiple payment lines, you cannot mix general ledger and BP accounts. All payment lines for a transaction must be general ledger or BP accounts.

When you select OK on the Manual entry screen, the match status changes to AD. You can return to Manual entry for this transaction to review, modify, or use Undo matching to delete the manual entry for this transaction. However, after you validate the transaction and generate the payment, you can no longer modify the transaction.

Manual entry is also available to review or modify transactions with an AS status that were matched using the search term list.

For payments

If you selected a payment in the Payments grid and you have a remaining amount, you can also create a manual entry for the remaining amount.

This is typically for bank charges: If the bank debits the charges directly on the transaction, the statement transaction amount is larger than the payment amount. In this case, you would select the existing payment in the Payments grid and create a Manual entry against a general ledger account for the remaining amount.

Enter a range of amounts to search for possible open items within those amounts.

Enter a source document to narrow the search for possible open items.

Select a BP type, Customer or Supplier, to narrow the search for open items.

Enter a BP number to search for open items related to that BP number.

Enter one or two BP names to search for open items that match one or both names.

BP names are automatically wild carded.

This field displays the number of results for entered criteria. This field updates automatically as criteria are entered, removed, or changed. The numbers are compared to open item transaction amounts without considering currency. BP name and invoice numbers are automatically wildcarded.

Enter a range of amounts to search for possible open items within those amounts.

Enter a payment number to search for that payment.

Enter a number of days to limit search results to payments with an accounting date not older than the number entered. Use this to restrict the results to the most current payments only.

Select a BP type, Customer or Supplier, to narrow the search for open items.

Enter a BP number to search for open items related to that BP number.

Enter one or two BP names to search for open items that match one or both names.

BP names are automatically wild carded.

This field displays the number of results for entered criteria. This field updates automatically as criteria are entered, removed, or changed. The numbers are compared to open item transaction amounts without considering currency. BP name and invoice numbers are automatically wildcarded.

Select Complete transaction to suppress payment creation for the selected transaction. For example if the open items associated with the bank statement transaction have been settled outside of the bank statement import function. In other words, if a payment transaction included in the bank statement already exists as a payment in Sage X3.

The transaction status is Manually completed and no payments are created for a manually completed transaction.

The action Complete transaction is active when the transaction status is Not validated but has already been matched or when the transaction status Partially validated.

After a payment has been generated, click this action to view the related payment.

Select Activate log file to create a log file for the automatic matching. It displays the settings used in the matching and details for the resulting matches to better understand why a match has or has not been performed. Avoid using the log file when matching the entire statement. Use Match transaction to investigate single transactions instead.

This is a temporary setting. Closing and re-opening the screen resets this option.

Limitations

The following functional limitations apply to the bank statement import process.

• Format
  Only MT940, CAMT.053/.054, BAI2, and CSV (AR Lockbox/generic) bank statement formats are supported.
  See the how to guide for detailed information about supported formats and limitations.
• Controls
  There are no controls on imported bank account balance, statement number, or company name. There is no check or control if the currently imported statement follows the data of the previous import, (i.e., next statement no.).
• Currency handling
  Sage X3 bank account currency and bank statement currency must be the same. And you need to consider:
  
  • If the statement currency and company currency are the same, automatic and manual matching considers open items in company and in foreign currency. Open items matched to the same transaction must have the same currency.
  • If the statement currency and company currency are different, (i.e., USD bank account for a GBP company), then the statement currency and open item currency must be the same to be considered in the automatic or manual matching. You cannot match, for example, a USD payment to a GBP open item.
• Single bank account import files
  One import file can contain multiple statements from the same bank account. You cannot mix statements from different bank accounts in one file.
• Prepayment open items
  Prepayment open items are excluded from matching and are not displayed on the Process bank transactions screen.
• Open items linked to a factor
  These are not considered in the automatic matching and are not displayed in the manual matching.
• Netting a BP that is a supplier and customer
  A payment is matched to both supplier and customer invoices.
• Late charges
  Neither automatic matching nor manual matching calculate or check on late charges (only on discounts).
• Transactions marked Return debit (RD) and Return credit (RC)
  Transaction flagged with debit/credit marks RD and RC in segment :61: concern payment reversals. Currently, these transactions should be posted to the suspense account and not matched to open items. See the section Understanding electronic bank statement format basics.
• SEPA Direct Debit returns (SDD)
  There is no automatic handling for SDD returns.
• Access control
  Controls on access codes, validity of the time range, etc., are only performed before payment creation. If there are issues, the entry or the settings can be corrected accordingly.
• Discount modes
  Automatic discount calculation in the bank statement import supports calculation modes Breakdown by VAT (invoice level), Breakdown by VAT (account level), and Discount on VAT (exempt)/Global in the (DEPMGTMOD Discount management mode parameter (TC chapter, INV group). For other cases, Breakdown by VAT (account level) is used as a fallback.
• BAI2 file format limitations
• Type codes linked to status or summary record types are not blocked for the import.
• If a type code linked to a Record type 16 is not listed in the Bank import type code (BSIIMTC) function, the file import fails. You need to add the type code to be able to import the file.