PMIS Account Banking SEPA

Extends OCA payment orders with a company-controlled SEPA export format, structured remittance information, and vendor payment-reference preferences.

Table of contents

Features

Payment lines gain purpose GDSV (Purchase Sale Of Goods And Services), which is the default for new lines.
Vendor invoices and credit notes prefer payment_reference, then ref, then the document number for direct payment-order communication. Full communication still delegates to OCA's handling of reversals and partial payments.
Use PMIS SEPA XML Format is stored per company and defaults to enabled. Disabling it delegates file generation and remittance blocks to OCA; the purpose default and vendor communication preferences still apply.

With the company setting enabled, the custom full-file generator handles sepa_credit_transfer. It first calls the inherited generator, so upstream validation still applies. Other payment methods return the inherited file; however, any inherited generator calling generate_remittance_info_block still receives the PMIS remittance block while the setting is enabled.

The credit-transfer generator accepts PAIN version prefixes pain.001.001.02, pain.001.001.03, pain.001.001.04, and pain.001.001.05, plus the exact version pain.001.003.03. The configured payment method must also provide the appropriate schema. Other versions raise an error.

Payments are grouped by requested payment date, priority, local instrument, and category purpose. Each transaction requires a recipient bank account. Its purpose comes from the first underlying payment line. EndToEndId is the company country code followed by 99; it is not a unique invoice identifier.

Remittance information

PMIS always creates a structured RmtInf/Strd block. The creditor reference comes from the move payment reference on the last underlying payment line, falling back to that line's communication, then NO_REF. Ordinary spaces are removed and the field is prepared with a 35-character limit. A grouped payment therefore does not export every underlying invoice reference.

Additional information is the translated text Invoice payment followed by that move's payment reference, or NO_INFO, with a 140-character limit. It does not use the communication fallback. The first payment line's communication type supplies the structured-reference issuer.

The exact pain.001.001.02 flavor uses CdtrRefTp/CdtrRef; other flavors use Tp/Ref. Exceptions preparing either text field are logged and replaced with ERROR. Review the exported content as well as schema validation: these placeholders do not establish a valid payment reference or bank acceptance.

Configuration

Declared dependencies are account_payment_sale, account_banking_sepa_direct_debit, account_banking_pain_base, account_payment_order, and pmis_ux. Credit-transfer export also requires a payment method and generator supplied by the OCA SEPA credit-transfer addon; this addon does not declare that addon as a direct dependency.

Open Settings > PMISuite Settings > Banking SEPA Settings for the company.
Review Use PMIS SEPA XML Format, which is enabled by default. The setting container is labeled PMIS SEPA Direct Debit, although the custom full-file generator handles credit transfers.
Configure the payment mode, originating bank account, company country, and a PAIN version accepted by the receiving bank.

Usage

Prepare a payment order through the OCA payment-order workflow.
Check each payment line's purpose, communication, and recipient bank account.
Generate the file and review its references, particularly for grouped payments or missing vendor payment references.
Submit the file through your bank's own import workflow. This addon generates files; it does not transmit payments or guarantee that a bank accepts them.