Sequence number statement of account on paper or Julian date or zeros. 63 up to 65, and communication as of pos. 62 = 1 type of structured communication in pos. Value date or 000000 if not known (DDMMYY)Ĭommunication type: 0 = none or unstructured 1 = structuredĬommunication zone: - if pos. Reference number of the bank This information is purely informative. If there are more than 9,999 details relating to one single transaction, the number goes up to 0000 and then 0001. If there are more than 9,999 transactions, the number goes up to 0000 and then 0001.ĭetail number starts at 0000 and is increased by 1 for each movement record for the same continuous sequence number. The detailed structure of all records can be found in Annexe I of the Coded statement of account (CODA) starting at page 14.Įxample: Data record 2.1 - "movement record" PositionsĬontinuous sequence number Starts at 0001 and is increased by 1 for each movement record referring to another movement on the daily statement of account. A transaction’s movement and information data stored in the Raw XML field on the Transaction record could look like follows: in case of charges for cross-border credit transfersĪ transaction contains detailed data in the form of movement records, which can in turn have information records with additional information. The records in a separate application keep type 6.ĭetail of 2, simple account with detailed data The records in a separate application keep type 7.ĭetail of 7 The records in a separate application keep type 9. In that case, one will speak of a ‘separate application’. The customer may ask for a separate file containing the detailed data. : the total amount of a series of credit transfers with a structured communication As a matter of principle, this type will also be used when no detailed data (type 6 or 7) is following.ĭetail of 2, simple amount without detailed data Normally, data of this kind comes after type 2. However, the customer may ask for detailed data to be included into his file after the overall record (type 1).Īmount as totalised by the bank e.g. As a matter of principle, this type is also used when no detailed data is followi (type 5).ĭetail of 1 Standard procedure is no detailing. a file regrouping payments of wages or payments made to suppliers or a file regrouping collections for whic the customer is debited or credited with one single amount. : an individual credit transfer (free of charges)Īmount as totalised by the customer e.g. Only the underlying transactions subtypes 6 or 7 lead to Transaction records in Salesforce. When the transaction type code starts with 2 or 3, the transaction is treated as a summary transaction and ignored. However, if subtype 5 is present, FinDock skips the type 1 entry and instead creates a Transaction record with the details from the subtype 5 entry. When the transaction type code starts with 0 or 1, FinDock creates Transaction records for the transaction entries. A transaction can consist of several cash movements, for instance when fees are deducted or exchange rates are applied, captured by movement records. Transaction types Ī CODA file consists of transactions identified by a transaction ID. So unlike with a CSV or Excel file, each row in the file can have a different structure, and not every row is a separate transaction. This is complicated by the fact that, in the case of CODA, what data is available can be determined by the content of other columns. Fixed Width files are arranged in columns, but instead of the columns being separated by a character like a comma or semicolon every row is the same length. Fixed Width files ĬODA files are structure Fixed Width data files. This document contains every detail on CODA, so it’s worth checking out if you wish to understand CODA reconciliation further. CODA file structure įinDock parses CODA files following the structure set out by Febelfin, the Belgian Federation for the Financial sector, as documented in the Coded statement of account (CODA) description (PDF). Like other Bank statements, CODA files are uploaded to a specific Salesforce Chatter group to be parsed by FinDock.įinDock requires a SEPA target with the bank account for which you want to reconcile a CODA file.įor more information on the general Processing bank statement processing flow, please read our Processing bank statements article. FinDock turns CODA files into a Transaction Set with Transaction records that are processed using Guided Matching. The reconciliation process allows you to update and confirm your payment data in Salesforce. CODA, or geCOdeert DAgafschrift is a bank statement or ‘Coded statement of account’ filetype used in Belgium.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |