ISO20022 Payment in D365FO for Norway – Part 3 (Company setup)

In this post there will be step by step setup requiring to enable a company to apply ISO20022 payment. Once you have imported ISO20022 from Microsoft repositories ISO20022 Payment in D365FO for Norway – Part 2 (Config) – DynFOTech, you need to activate provided configuration for each company in order to generate or import ISO20022 file:

  • Legal entity (Organization administration > Organizations > Legal entities)
    • Name: Company name.
    • Address: The legal entity need to have a primary address with “Country/region”, “Street” and “Zip/postal code”. Country must have a value for ISO field (e.g. ISO code for Norway is “NO”.
Legal entities – Information
Norway ISO code

This information will be found on Pain.001 and Camt054 files as follows:

Pain.001 file
Camt.053 file

And on “Attending note” while generating Pain.001 file:

Attending note
  • Contact information
    • Phone: Primary phone number.
    • Fax: Primary fax number.
Contact information

Contact information will be found on cover letter excel file:

Cover letter
  • Bank account: Company bank account.
  • Giro account : Bank account number.
Legal entity_Bank account information
  • Tax registration number: Use organization number for this field. If the company is tax registered, you can add “MVA” after the organization number.
Company tax registration number
  • Return format error codes (Account payable > Setup > Payment setup > Return format error codes)

External status reason codes using for interpreting group status code with additional information that will show up while importing payment files. Following return error codes can be used:

CodeNameDescription
AC01IncorrectAccountNumberAccount number is invalid or missing.  
AC03InvalidCreditorAccountNumberCreditor account number invalid or missing
AC06BlockedAccountAccount specified is blocked, prohibiting posting of transactions against it.
AC07ClosedCreditorAccountNumberCreditor account number closed
AG06InvalidCreditorAgentCountryCreditor agent country code is missing or invalid
AG08InvalidAccessRightsTransaction failed due to invalid or missing user or access right
AM01ZeroAmountSpecified message amount is equal to zero
AM03NotAllowedCurrencySpecified message amount is an non processable currency outside of existing agreement
AM11InvalidTransactionCurrencyTransaction currency is invalid or missing
AM14AmountExceedsAgreedLimitTransaction amount exceeds limits agreed between bank and client
BE04MissingCreditorAddressSpecification of creditor’s address, which is required for payment, is missing/not correct (formerly IncorrectCreditorAddress).
BE07MissingDebtorAddressSpecification of debtor’s address, which is required for payment, is missing/not correct.
BE11InvalidCreditorCountryCreditor country code is missing or invalid
BE22MissingCreditorNameCreditor name is missing
CH03RequestedExecutionDateOrRequestedCollectionDateTooFarInFutureValue in Requested Execution Date or Requested Collection Date is too far in the future
CH20DecimalPointsNotCompatibleWithCurrencyNumber of decimal points not compatible with the currency
DU02DuplicatePaymentInformationIDPayment Information Block is not unique.
DUPLDuplicatePaymentPayment is a duplicate of another payment
NARRNarrativeReason is provided as narrative information in the additional reason information.
RC02InvalidBankIdentifierBank identifier is invalid or missing.
Generic usage if cannot specify between debit or credit account
RC03InvalidDebtorBankIdentifierDebtor bank identifier is invalid or missing
RC04InvalidCreditorBankIdentifierCreditor bank identifier is invalid or missing
RC07InvalidCreditorBICIdentifierCreditor BIC identifier is invalid or missing
RR01MissingDebtorAccountOrIdentificationSpecification of the debtor’s account or unique identification needed for reasons of regulatory requirements is insufficient or missing
RR02MissingDebtorNameOrAddressSpecification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing.
RR03MissingCreditorNameOrAddressSpecification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing.
RR04RegulatoryReasonRegulatory Reason
RR09InvalidStructuredCreditorReferenceStructured creditor reference invalid or missing.
Return format codes

Example:

Pain.002 file with return format code
  • Return format status mapping (Account payable > Setup > Payment setup > Return format status mapping)

External payment transaction status and group status codes existing in Pain.002, Camt.053 and Camt.053 files:

DescriptionPayment statusReturn status
BookedApprovedBOOK
AcceptedSettlementCompletedReceivedACCC
AcceptedCustomerProfileReceivedACCP
AcceptedFundsCheckedReceivedACFC
AcceptedSettlementCompletedDebitorAccountReceivedACSC
AcceptedSettlementInProcessReceivedACSP
AcceptedTechnicalValidationReceivedACTC
AcceptedWithoutPostingReceivedACWC
AcceptedWithoutPostingReceivedACWP
PartiallyAcceptedTechnicalCorrectReceivedPATC
PendingReceivedPDNG
ReceivedReceivedRCVD
RejectedRejectedRJCT
Return format status mapping

Example:

Camt.054 payment status
  • Payment format code sets (Account payable > Setup > Payment setup > Payment format code sets)

Service level codes and local instrument needs to be defined and associates to method of payment. Some example for local instrument are as follows:

CodeTypeNameInformation
NURGService levelNonurgentPaymentPayment must be executed as a non-urgent transaction, which is typically identified as an ACH or low value transaction.
NUGPService levelNonurgentPriorityPaymentPayment must be executed as a non-urgent transaction with priority settlement.
URGPService levelUrgentPaymentPayment must be executed as an urgent transaction cleared through a real-time gross settlement system, which is typically identified as a wire or high value transaction.           
SEPAService levelSingleEuroPaymentsAreaPayment must be executed following the Single Euro Payments Area scheme.
INLocal instrumentInternational paymentCrossBorderCustomerCreditTransfer
Payment format code sets
Payment format code sets
  • Method of payment – Vendor (Account payable > Setup > Payment setup > Method of payment)
  • Payment status: Approved. Choose a payment status required for posting of payments.
    • Payment type: Electronic payment.
Methods of payment – vendors
  • Bank account: Select a bank account that is already activated for payment with the bank. Following fields should be updated:
    • Company ID: A specific value that is agreed with bank to send and receive payment file.
    • IBAN
    • SWIFT Code
    • Division: A specific identifier for division of bank account. This field can be mandatory in regards to bank requirements.
    • Address: Once this field is updated with a value, you can update division field.
Methods of payment – vendors- Payment account
Methods of payment – vendors- Bank account
  • Payment specification (Account payable > Setup > Payment setup > Method of payment > Payment specification)

You need add domestic and foreign payment with local instrument and service level:

Payment specification

Domestics:

Payment specification – Domestics

Foreign:


Payment specification – Foreign
  • File formats > Generic electronic Export format : Yes
  • File formats > Export format configuration : ISO20022 Credit transfer (NO)
  • File formats > Return format secondary configuration: Camt.054
  • File formats > Return format configuration : Pain.002
Methods of payment – vendors – File formats

Note: Payment control can be used to define mandatory fields (e.g. Payment ID is mandatory)

Note: Payment attributes can be used to define attributes for the method of payment (e.g. Third-party bank)

  • Method of payment – Customer (Account receivable > Setup > Payment setup > Method of payment)
  • Payment status: Received. Choose a payment status required for posting of payments.
    • Payment type: Electronic payment.
Methods of payment – customers
  • Bank account: Select a bank account that is already activated for payment with the bank. Following fields should be updated:
    • Company ID: A specific value that is agreed with bank to send and receive payment file.
    • IBAN
    • SWIFT Code
    • Division: A specific identifier for division of bank account. This field can be mandatory in regards to bank requirements.
    • Address: Once this field is updated with a value, you can update division field.
Methods of payment – customers – payment account
Methods of payment – customers – Bank account
  • File formats > Generic electronic Import format : Yes
  • File formats > Import format configuration : Camt.054
Methods of payment – customers – File formats
  • Bank statement format: In order to import electronic bank statement and automatic reconciliation, you need to setup bank statement format ISO20022 (Camt.053)
Bank statement format

Then provide this statement format for bank account that you want to activate advanced bank reconciliation:

Bank account – reconciliation

Then, the legal entity is activated for importing and exporting ISO20022 bank files.

Useful links:

https://docs.microsoft.com/en-us/dynamics365/finance/cash-bank-management/tasks/vendor-payment-overview

https://docs.microsoft.com/en-us/dynamics365/finance/accounts-receivable/tasks/establish-customer-method-payment

https://docs.microsoft.com/en-us/dynamics365/finance/cash-bank-management/set-up-advanced-bank-reconciliation-import-process

2 Comments Add yours

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s