972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Finance

FINCAN Financial cancellation

The UN/EDIFACT message a customer, or a party with authority over its payments, sends a bank to cancel a financial message or transaction.

Sent by
Ordering customer, its agent or an authorized third party
Received by
Ordered bank
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT FINCAN message?

FINCAN is the UN/EDIFACT financial cancellation message. The directory defines it as a message sent by the ordering customer, or a payer or agent on its behalf, or a third party with authority over the customer's payments, to the ordered bank to request cancellation of a given financial message or transaction.

Cancellation is only possible before the bank executes the payment, so timing is critical. The bank reports whether the cancellation succeeded, typically with a BANSTA. Companies use FINCAN when a payment file was sent in error, duplicated or contains wrong beneficiary details.

How the EDIFACT FINCAN message worksDiagram of the UN/EDIFACT FINCAN Financial cancellation message. Ordering customer, its agent or an authorized third party sends it to ordered bank. It usually follows PAYMUL, PAYORD and PAYEXT. It is usually followed by BANSTA. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG4 loop with LIN (Line item). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT FINCAN message worksFinancial cancellation: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSPAYMULMultiple payment orderPAYORDPayment orderPAYEXTExtended paymentorderFINCANSENDEROrdering customer, itsagent or an authorizedthird partyRECEIVEROrdered bankCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYBANSTABanking status2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage FINCANUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG4 · repeats up to 9,999LINLine item+ 5 conditional groups, starting with:RFFFIINADAUTBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for FINCAN. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT FINCAN message worksDiagram of the UN/EDIFACT FINCAN Financial cancellation message. Ordering customer, its agent or an authorized third party sends it to ordered bank. It usually follows PAYMUL, PAYORD and PAYEXT. It is usually followed by BANSTA. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG4 loop with LIN (Line item). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT FINCANmessage worksFinancial cancellation: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSPAYMULMultiple payment orderPAYORDPayment orderPAYEXTExtended payment orderFINCANSENDEROrderingcustomer, itsagent or anauthorized thirdpartyRECEIVEROrdered bankCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYBANSTABanking status2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message FINCAN (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG4 · repeats upto 9,999LINLine item+ 5 conditional groups, starting with:RFFFIINADAUTBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for FINCAN.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends FINCAN, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around FINCAN and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Cancelling a duplicated payment file
  • Stopping a payment with wrong beneficiary details
  • Withdrawing payments before execution

Where it fits in the message flow

Usually follows PAYMUL Multiple payment orderPAYORD Payment orderPAYEXT Extended payment order
This message FINCAN Financial cancellation
Usually followed by BANSTA Banking status

Structure

Mandatory segments in FINCAN (directory D.21A)

In UN/EDIFACT directory D.21A, the FINCAN message has 19 segment positions arranged in 6 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • SG4 (LIN)
  • UNT

Practical example

FINCAN in practice

A treasury analyst notices that the morning's supplier payment file was sent twice. Before the bank's processing cut-off, the treasury system sends a FINCAN referencing the duplicate PAYMUL. The bank cancels the duplicate and confirms with a BANSTA, and the analyst records the incident.

Implementation

Implementation considerations for FINCAN

  • Act before the bank's execution cut-off.
  • Reference the original message or transaction exactly.
  • Confirm the outcome from the bank's status report.
  • Apply the same authority controls as for payment approval.

How ECOM helps

Automate FINCAN with ECOM

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related finance messages

All 37 finance messages

Need help with FINCAN?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us