%20(1).png)
FAQs on Online Banking (FinAPI)
Question
Why aren't invoices automatically assigned via the FinAPI interface?
Re:
đź’¶ Accounting
⚙️ Administration
Short answer
Automatic allocation occurs only if the sender's name, IBAN, payment description, and amount clearly match an open c-entron invoice. If there are discrepancies, the payment receipt remains open and must be allocated manually.
Solution / Overview
Please check the following points:
- Does the name of the payer match the customer name in the address database?
- Is the IBAN used in the wire transfer stored in the customer's address master data?
- Does the payment description include a unique c-entron invoice number?
- Does the amount transferred correspond exactly to a single invoice (not a consolidated or partial payment)?
- Is version 2.0.2509.68 or later in use (relevant for stores with different number ranges)?
👉 Only when all criteria are clearly met does FinAPI automatically match the incoming payment to the corresponding invoice.
Background
The FinAPI interface matches every incoming payment against the open invoices in the c-entron system based on several criteria (sender name, IBAN, payment reference, amount). Automatic matching occurs only if all data is consistent. If the matches are ambiguous or individual fields differ, the transaction is intentionally left open so that a manual review can be performed—this prevents incorrect postings in cases of similar customer names or identical amounts.
Common Mistakes
Common causes or misunderstandings include:
- The payer is using a different company or personal name that is not listed in the address database.
- The customer's second or new bank account details are not maintained in the address master.
- The invoice number is missing from the payment description or is misspelled.
- Batch transfers are recorded as a single amount, without a clear breakdown.
- An outdated version of c-entron is in use (prior to 2.0.2509.68 for stores with different number ranges).
👉 In these cases, the payment receipt remains marked as "unassigned" and must be manually updated—for example, in the case of bulk transfers that are split across multiple documents.
Tip
For customers with multiple bank accounts or varying company names, all known IBANs and spellings should be stored in the address master. This will significantly increase the success rate of automatic assignment. For recurring bulk transfers, it is recommended to agree with the customer on a clear structure for the payment reference (e.g., “RG 12345 + RG 12346”).
Related Topics
Question
Why aren't transaction records being retrieved anymore since the bank merger/BIC change, even though the account is still the same?
Re:
đź’¶ Accounting
⚙️ Administration
Short answer
If the BIC or bank details change following a bank merger or restructuring—even if the IBAN remains the same—FinAPI no longer recognizes the account as the same internally. The existing link no longer works. New bank details must be created in c-entron, and the old FinAPI account must be linked again.
How can I tell if there's a problem?
The account transaction query is running—however, no new records are being saved.
Sales are cut off as of a specific date (often the date of the bank merger).
A manual update does not report an error, but it does not update anything.
A newly created link for the same account is generating revenue (again).
Even if the IBAN and account number remain unchanged: A change in the BIC (e.g., due to a merger of two banks or a transition to a different data center) causes FinAPI to treat the connection internally as a new bank. The old connection remains technically active but no longer provides any data—without any obvious error being displayed.
Solution / Overview
- Check whether the customer’s bank has merged or whether the BIC has changed (e.g., using the Deutsche Bundesbank’s official BIC search tool or a notice from the bank).
- In c-entron, create a new bank account entry for the account in question—even if the IBAN and account number are the same.
- Reconnect the account via the FinAPI dialog (Consensus / Reconfigure Connection).
- Check whether retroactive sales can be reloaded starting from the merger date by manually extending the retrieval period.
- The old bank account can be deactivated or archived after it has been successfully verified.
Background
FinAPI identifies bank accounts internally using the BIC (and, if applicable, other bank parameters). If the BIC changes—even if the IBAN remains the same—the existing account is not automatically migrated in FinAPI. The account still appears as linked in the interface, but in the background it is connected to an outdated or invalid bank interface. As a result, new transactions are not retrieved without an obvious error occurring.
Tip
Banks typically notify customers of BIC changes by mail or through their online banking inbox. If you’re unsure whether a merger has taken place, you can check the bank’s current BIC in the Bundesbank’s BIC directory (www.bundesbank.de).