This FAQ page helps you resolve common questions and issues in NAVAX Payment more quickly. The content is structured as short checklists: if something is “not considered”, you can verify step by step which prerequisite is missing.
Exports
In this section you will find common questions and typical root causes related to NCP Exports (creating and exporting payment files).
How to enable or disable batch booking?
With Batch Booking you control whether payments are grouped in the payment file (batch booking) or shown as individual payments. How your bank processes this setting depends on the selected format and the bank’s requirements.
Setup
Open NCP Exports Setup.
Open the XML schemas using the XML Schemas action.
Select the schema you want and choose Edit.
In the General section you will find the Batchbooking option.
Select the required value in the dropdown and save.
Note
If the bank creates individual transactions despite batch booking being enabled (or vice versa), also check the bank’s requirements and the XML/payment format being used.
How do I set up “Structured Address” in the XML schema?
For newer SEPA payment files it can be required to provide addresses in a structured way. To do so, structured address output must be enabled in the XML schema.
Setup
Open NCP Exports Setup.
Open the XML schemas using the XML Schemas action.
Select the schema you want and choose Edit.
In the schema, set the fields Originator Address and/or Recipient Address to Yes - Structured.
When Yes - Structured is enabled, the schema creates additional lines/elements for the structured address, for example:
StreetNm (street)
TwnNm (city/town)
Ctry (country code)
Note
Make sure the address data in the master data (street, city, and country/region code) is maintained—otherwise the structured fields may be empty.
Payment Discounts
Payment discounts are only applied automatically if the related entry and the payment meet the payment discount conditions.
Checklist: Why is the payment discount not applied?
Entry is open: Payment discounts are only relevant for open entries. If the entry is already applied/closed, no payment discount will be applied.
Payment within the discount date: Check on the entry whether the payment date is within the discount period. You can also verify this on the Apply Customer Entries / Apply Vendor Entries pages.
Remaining discount available: A payment discount is only applied if the entry has an amount greater than 0.00 in Remaining Pmt. Disc. Possible.
Discount date / discount period: Payment discounts are only applied within the discount period; the relevant date is shown on the entry in Pmt. Discount Date.
Typical verification steps
Open the affected customer/vendor ledger entry and verify that it is still open.
Check Pmt. Discount Date, Remaining Pmt. Disc. Possible, and whether the payment date is within the discount period.
Apply the entry again and validate the calculated amounts on the apply/journal lines.
Payment Discount Tolerance
Payment discount tolerance allows payment discounts to be considered even if the payment is slightly outside the payment discount date—provided the tolerance is configured in the setup.
Why is payment discount tolerance not applied?
Entry is open: Payment discount tolerance is only relevant for open entries. If the entry is already applied/closed, no tolerance can be applied.
Payment within tolerance: Tolerance is only considered if the payment date falls within the allowed tolerance. Verify this on the entry or on the Apply Customer Entries / Apply Vendor Entries pages.
Tolerance period is set: In General Ledger Setup, the Pmt. Disc. Tolerance Period field must contain a value.
Note
If you want to use payment discount tolerance, make sure the definition in General Ledger Setup is intentionally configured and appropriate for your company.
Imports
In this section you will find common questions and typical issues related to NCP Imports (importing bank statements and matching/reconciling entries).
First steps when something isn’t working
Correct format: Verify that the imported file matches the expected format (e.g., camt.052/053/054, MT940).
For more information, see Setup, General, Bank Account Setup.
Bank account mapping: Verify that the bank account is set up correctly and that the file is assigned to the correct account.
For more information, see Setup, General, Bank Account Setup.
Matching result: If transactions are imported but no automatic matching happens, check open entries, amounts, and remittance information/references.
Related information
Setup, General, Bank Account Setup The NCP Bank Account Setup page is the central management interface for all bank accounts used in NAVAX Payment Processing. Here you enter and maintain all bank master data required for payment processing, exports, and imports in Microsoft Dynamics 365 Business Central...
Setup, Exports, XML Schemas The XML format is the Europe-wide recognized standard for payment transactions and is actively promoted by the European Payments Council (EPC) and the EU. The goal is to standardize the multitude of national payment formats and, in the long term, to fully replace them with the XML format. This harmonizes and simplifies the processing of transactions both between banks and for end customers from a technical perspective...
FAQ and Troubleshooting
