Templating Language Specification

Template Language for Mindbow General Ledger Interface Files.     Version 1.02

Note: This is an initial version of the templating language, which should be suitable for most interfaces. We will expand the language as we need to meet customer requirements. (contact Mindbow support for latest specification)

Templates can be produced by your accounting software supplier, or by Mindbow if we are provided with the Interface requirements.
Since the template controls the interface file, it means that changes can be made without the need to reprogram our software.
In most cases we will be unable to test any interface specific to each and every version of every  accounting package. Minor changes can be made by the user or their accounting system support consultants.

Tokens (instructions or data items) are enclosed in any set of brackets    { }  or    [ ]   or    ( )   or    < >
Only one set should be used throughout the file. Choose a set which is not part of the normal text in the interface file.
The very first character in the template file will determine the brackets to be used for Tokens..

In the description below we use { } throughout.


The template is read, and the output file created as the template is followed. Data tokens are substituted by data from the database. Literal characters in the template are written to the file.

Supported Tokens:

{Comment} anything on this line is ignored when creating the interface file. Used to document the template for those who follow.
{Date Format}{format} If this line omitted, the format  dd/mm/yyyy is assumed. Uses standard Excel/vba date formats. The date format token should precede the interface description.

Interface file sections: The Interface file can have three sections, the header, a repeating transaction section and a footer. Layout is as follows:

{Start} All literal Text after this line will be included in the output file.

The Interface file Header (non repeating) section goes here


Transaction information, repeated once for Each GL Asset Class code, goes here. Normally, there will be two interface transactions described, one for the expense, and one for the contra posting.

{End Trans}

Interface footer if required goes here.

{End} This is the end of the interface and any further template text is ignored.

Tokens that get substituted from the Database or software.   

WhiteSpace Tokens.

Tabs and spaces can be “invisible” so to make them easily visible in the interface file the following will apply. All other tabs and spaces will be ignored.
Use {b} for a space between words.

{Tab} generates a Tab character.
{b} or {Space} will generate a single space character.

Transaction Tokens in the header or footer will be generated from the first or last transaction respectively.

{Date} Transaction date – the last day of the period being posted.

{SysDate} Current computer system date.

{AccDepnExpense} Depreciation expense from the Accounting ledger for the chosen period

{TaxDepnExpense} Depreciation expense from the Tax ledger for the chosen period

{AssetClass} The GL Asset Class code. This would normally be a comment field.

{AccDepnExpenseAccount} The General Ledger Account for depreciation expense from the Accounting Ledger.

{TaxDepnExpenseAccount} The General Ledger Account for depreciation expense from the Tax Ledger.

{AccAccumDepnAccount} The General Ledger Account for accumulated depreciation from the Accounting Ledger.

{TaxAccumDepnAccount} The General Ledger Account for accumulated depreciation from the Tax Ledger.

See Also:  Sample Template