Skip to main content

FiDAViSta Format

The FiDAViSta format is an XML-based payment file format designed for integration with FiDAViSta accounting and financial management systems. This format supports complex payment structures with comprehensive metadata.

Overview​

FiDAViSta format is a structured XML format that provides:

✅ XML-based structure - Industry-standard hierarchical format
✅ Multiple data groups - Header, Payments, Statements, Payment Status
✅ Banking integration - Direct connection with bank systems
✅ Accounting system support - FiDAViSta software integration
✅ Payment tracking - Unique identifiers for status monitoring
✅ Multi-currency support - International payment capabilities

File Structure​

A FiDAViSta file consists of a Root element containing several optional groups:

<Root xmlns:xsi="..." xsi:noNamespaceSchemaLocation="...v0001.xsd">
  <Header>...</Header>
  <Payment>...</Payment>
  <Payment>...</Payment>
  <PmtStat>...</PmtStat>
  <Statement>...</Statement>
</Root>

Main Elements​

ElementPurposeStatus
HeaderFile metadata and preparation info✅ Available
PaymentPayment order information✅ Available
PmtStatPayment status tracking🔜 Coming soon
StatementBank account statements🔜 Coming soon

Header Element​

The Header contains file preparation metadata.

Fields​

TagLengthTypeRequiredDescription
Timestamp17xs:stringOptionalFormat: YYYYMMDDHHMMSSsss
Example: 20231215143025000
From0-70xs:stringOptionalPreparer's identifier
Extension-ExtensionTypeOptionalAdditional custom elements

Example​

<Header>
  <Timestamp>20231215143025000</Timestamp>
  <From>ACCOUNTING_SYSTEM_ID</From>
</Header>

Payment Element​

The Payment element contains detailed payment order information.

Core Payment Fields​

TagLengthTypeRequiredDescription
ExtId0-10SwiftStringOptionalUnique payment ID in external system
DocNo1-10SwiftStringMandatoryPayment/document number
RegDate10xs:dateOptionalRegistration date (YYYY-MM-DD)
TaxPmtFlg1xs:stringMandatoryY = Tax payment
N = Normal payment
Ccy3CurrencyTypeMandatoryPayment currency (EUR, USD, etc.)
Amt1-12AmountTypeMandatoryAmount with decimal (e.g., 1000.50)
PmtInfo0-140EksStringOptionalPayment description
BankInfo0-140xs:stringOptionalInformation for the bank

Payer Fields​

TagLengthTypeRequiredDescription
PayLegalId0-20LegalIDTypeOptionalPayer's registration/personal ID
PayAccNo1-34AccountMTypeMandatoryPayer's account number
PaySubAccNo0-34AccountOTypeOptionalPayer's sub-account
DebitCcy3CurrencyTypeOptionalDebited currency

Beneficiary Set (BenSet)​

TagLengthTypeRequiredDescription
BenExtId0-5SwiftStringOptionalUnique beneficiary ID in payment
BenAccNo0-34AccountOTypeOptionalBeneficiary's account
BenSubAccNo0-34AccountOTypeOptionalBeneficiary's sub-account
BenAccIbanFlg0-1xs:stringOptionalY = IBAN verification
Default: N
BenName1-105EksStringMandatoryBeneficiary's name
BenLegalId0-20LegalIDTypeOptionalBeneficiary's registration ID
BenAddress0-70EksStringOptionalBeneficiary's address
BenCountry2CountryTypeMandatoryISO 3166 country code (e.g., LT)

Beneficiary's Bank​

TagLengthTypeRequiredDescription
BBName0-35EksStringOptionalBank name
BBAddress0-70EksStringOptionalBank address
BBSwift8-11SWIFTTypeOptionalBank SWIFT/BIC code
BBCode0-66BankCodeTypeOptionalBank code (with CodeType attribute)

Intermediary Bank​

TagLengthTypeRequiredDescription
CBAcc0-34AccountOTypeOptionalCorrespondent account
CBName0-35EksStringOptionalIntermediary bank name
CBSwift8-11SWIFTTypeOptionalIntermediary SWIFT code
CBCode0-66BankCodeTypeOptionalIntermediary bank code

Payment Options​

TagLengthTypeRequiredDescription
Priority1xs:stringMandatoryN = Normal
U = Urgent
X = Express
Comm3xs:stringMandatoryOUR = Payer pays
BEN = Beneficiary pays
SHA = Shared
BudgCode0-10SwiftStringOptionalBudget revenue code

AMK Set (Balance Code)​

TagLengthTypeRequiredDescription
Opc1-3xs:stringMandatoryAMK balance code (digits only)
Amt1-12AmountTypeOptionalAMK code sum

Data Types​

Standard Types​

TypeMinMaxFormatDescription
xs:string0∞UnicodeStandard XML string
xs:date1010YYYY-MM-DDStandard XML date
xs:decimal--0-9.Decimal number

Custom Types​

TypeMinMaxCharactersDescription
SwiftStringType--0-9 A-Z a-z /-?:().,'+SWIFT X character set
EksStringType--0-9 A-Z a-z A-Ž /-?:().,'+Extended with Latvian/Latin
SWIFTType811A-Z 0-9SWIFT/BIC code
CurrencyType33A-ZISO currency code
AmountType1120-9.Amount (12 digits, 2 after decimal)
AccountMType134SwiftStringMandatory account
AccountOType034SwiftStringOptional account
LegalIDType020SwiftStringLegal/personal ID
BankCodeType--SwiftStringBank code with CodeType attribute
CountryType22A-ZISO 3166-1 alpha-2

Example: Simple Payment​

<?xml version="1.0" encoding="UTF-8"?>
<Root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
      xsi:noNamespaceSchemaLocation="fidavista_v0001.xsd">
  
  <Header>
    <Timestamp>20231215143025000</Timestamp>
    <From>ACCOUNTING_SYSTEM</From>
  </Header>
  
  <Payment>
    <ExtId>PAY001</ExtId>
    <DocNo>INV2023001</DocNo>
    <RegDate>2023-12-15</RegDate>
    <TaxPmtFlg>N</TaxPmtFlg>
    <Ccy>EUR</Ccy>
    <Amt>1000.50</Amt>
    <PmtInfo>Payment for services</PmtInfo>
    
    <PayAccNo>LT123456789012345678</PayAccNo>
    
    <BenSet>
      <BenName>John Smith</BenName>
      <BenAccNo>LT987654321098765432</BenAccNo>
      <BenCountry>LT</BenCountry>
      <BenAddress>Main Street 123, Vilnius</BenAddress>
    </BenSet>
    
    <Priority>N</Priority>
    <Comm>OUR</Comm>
  </Payment>
  
</Root>

Example: International Payment with SWIFT​

<?xml version="1.0" encoding="UTF-8"?>
<Root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
      xsi:noNamespaceSchema Location="fidavista_v0001.xsd">
  
  <Header>
    <Timestamp>20231215143025000</Timestamp>
    <From>ERP_SYSTEM</From>
  </Header>
  
  <Payment>
    <ExtId>INT001</ExtId>
    <DocNo>INTL2023001</DocNo>
    <RegDate>2023-12-15</RegDate>
    <TaxPmtFlg>N</TaxPmtFlg>
    <Ccy>USD</Ccy>
    <Amt>5000.00</Amt>
    <PmtInfo>International consulting fee</PmtInfo>
    
    <PayAccNo>LT123456789012345678</PayAccNo>
    <DebitCcy>EUR</DebitCcy>
    
    <BenSet>
      <BenName>ACME Corporation Ltd</BenName>
      <BenAccNo>US12345678901234567890</BenAccNo>
      <BenAccIbanFlg>N</BenAccIbanFlg>
      <BenAddress>456 Broadway, New York, NY 10013</BenAddress>
      <BenCountry>US</BenCountry>
      
      <BBName>Citibank N.A.</BBName>
      <BBSwift>CITIUS33</BBSwift>
      <BBAddress>399 Park Avenue, New York</BBAddress>
    </BenSet>
    
    <Priority>U</Priority>
    <Comm>SHA</Comm>
  </Payment>
  
</Root>

Payment Status Element (PmtStat)​

Coming Soon

Payment status functionality will be available soon. This element tracks payment execution status.

Planned Fields​

TagDescription
ExtIdReference to payment ID
BenExtIdReference to beneficiary ID
BankRefBank reference number
StatCodeStatus: E (Executed), R (Revoked), P (Processing), O (Other)
BookDateExecution date
InfoToCustomerStatus explanation/error message

Statement Element​

Coming Soon

Account statement functionality will be available soon for storing bank account statements.

Key Features​

Priority Levels​

CodeNameDescription
NNormalStandard processing
UUrgentExpedited processing
XExpressFastest processing

Commission Types​

CodeNameWho Pays
OURPayerAll fees paid by payer
SHASharedFees split between parties
BENBeneficiaryAll fees paid by beneficiary

Tax Payment Flag​

CodeMeaning
YTax payment
NNormal payment

Best Practices​

✅ DO​

  • Use proper XML encoding (UTF-8)
  • Validate against XSD schema
  • Include unique ExtId for tracking
  • Specify correct currency codes
  • Use IBAN format when possible
  • Provide complete beneficiary information
  • Include SWIFT codes for international transfers

❌ DON'T​

  • Use invalid XML characters
  • Exceed maximum field lengths
  • Mix up required/optional fields
  • Forget to specify TaxPmtFlg
  • Use incorrect date formats
  • Omit mandatory BenCountry code

FiDAViSta vs Other Formats​

FeatureFiDAViStaMOKESISTARESIS
FormatXMLTAB-separatedTAB-separated
ComplexityHighMediumHigh
FieldsVariable (XML)31 fields40 fields
SystemFiDAViStaGeneralInternational
TrackingExtId systemPayment numbersPayment numbers
StatusBuilt-in (PmtStat)SeparateNo
ValidationXSD schemaManualManual
Best forERP integrationGeneral useInternational

Integration with FiDAViSta Software​

FiDAViSta format is specifically designed for:

  • Accounting systems using FiDAViSta
  • ERP systems with FiDAViSta integration
  • Banking systems supporting FiDAViSta standard
  • Financial management software

Integration Steps​

  1. Generate XML from your FiDAViSta system
  2. Validate against XSD schema
  3. Export payment file
  4. Import to bank system
  5. Track status via PmtStat (when available)
  6. Reconcile using Statement (when available)

Schema Validation​

The FiDAViSta format requires XML schema validation:

<Root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
      xsi:noNamespaceSchemaLocation="fidavista_v0001.xsd">

The schema version is indicated by a 4-digit version number (e.g., v0001).

When to Use FiDAViSta​

✅ Use FiDAViSta when:

  • You use FiDAViSta accounting software
  • You need XML-based integration
  • You require payment status tracking
  • You want structured data validation
  • You need ERP system integration
  • You want comprehensive payment metadata

❌ Use other formats when:

  • Manual payment entry needed → XLS
  • Simple bulk imports → MOKESIS
  • Complex international routing → TARESIS
  • No FiDAViSta system → MOKESIS or XML

Support​

Need help with FiDAViSta format?

Next Steps​