PostTrans XML API for Sage 50 - Nominal Journal

The PostTrans XML API for Sage 50 posts Nominal Journals into Sage 50, from a simple XML file, submitted to import directory or IMAP e-mail account.
After posting the file is moved to a processed folder, and the Transaction Reference is added to the top of XML file. If the file fails validation, then the error/errors are appended to the top of the file. A user can then easily edit and resubmit to PostTrans XML API for Sage 50.

List of Tags/Entities for mapping are at bottom of page.

Click here for an overview of the XML API for Sage 50

Demonstration Video

The following demo shows Sage 200, but the principle is exactly the same:

PostTrans XML API for Sage 200 Nominal Journal

	0:00	Where to get help
	1:00	Where to import from
	1:40	Open example and walk tNominal Journal XML API
	4:00	Post Nominal Journal into Sage 200
	4:30	The proof

Example – 1000 Nominal Journal Amount.xml

    <?xml version="1.0" ?>
    <sage50Data>
       <settings>  <!-- Optional overide settings/mappings -->
          <companyCode>DEMO01</companyCode>
          <mappings>
          </mappings>
       </settings>
       
      <NomHeader>    
         <!-- ===== Header ==== -->
          
          <THDate>2017-02-20</THDate>   <!-- Date - Overide Heading Date, thus causing a new transaction on change -->
         <THRef>My Test using Cr/Db </THRef>   <!-- Text 30 - Overide Heading Ref, thus causing a new transaction on change -->
       
          <!-- using Sage API 50 post three line Nominal Journal user either 
                <TLAmount> or <TLDebit> and <TLCredit>
                to define the amounts which must balance -->        
    
          <NomLine>
             <TLDetails>Optional:Set the description on this line</TLDetails>   <!-- Text 60 - Details -->
             <TLExterRef>Optional:And an External ref</TLExterRef>   <!-- Text 30 - External Referance -->      
             <TLNomCode>1210</TLNomCode>   <!-- Credit -->
             <TLAmount>-100</TLAmount>
          </NomLine>
          <NomLine>
             <TLDetails>Another line of text</TLDetails> 
             <TLNomCode>4000</TLNomCode>  
             <TLAmount>50</TLAmount>    <!-- Debit -->
          </NomLine>   
          <NomLine>
             <TLDetails>Credit of 50</TLDetails> 
             <TLDepartment>1</TLDepartment>
             <TLNomCode>4001</TLNomCode>  
             <TLAmount>50</TLAmount>    <!-- Debit -->
          </NomLine>    
         </NomHeader>
    </sage50Data>

Example – 1010 Nominal journal CrDb.xml

    <?xml version="1.0" ?>
    <sage50Data>
       <settings>  <!-- Optional overide settings/mappings -->
          <companyCode>DEMO01</companyCode>
          <mappings>
          </mappings>
       </settings>
       
      <NomHeader>    
         <!-- ===== Header Sage 50 Journal ==== -->
          
          <THDate>2017-02-20</THDate>   <!-- Date - Overide Heading Date, thus causing a new transaction on change -->
         <THRef>My Test</THRef>   <!-- Text 30 - Overide Heading Ref, thus causing a new transaction on change -->
    
    
          <NomLine>
             <TLDetails>Optional:Set the description on this line</TLDetails>   <!-- Text 60 - Details -->
             <TLExterRef>Optional:And an External ref</TLExterRef>   <!-- Text 30 - External Referance -->
             <TLNomCode>1210</TLNomCode>  
             <TLDebit>100</TLDebit>
          </NomLine>
          <NomLine>
             <TLDetails>Credit 50</TLDetails> 
             <TLNomCode>4000</TLNomCode>  
             <TLCredit>50</TLCredit>
          </NomLine>   
          <NomLine>
             <TLDetails>Another Credit 50</TLDetails> 
             <TLDepartment>1</TLDepartment>
             <TLNomCode>4001</TLNomCode>  
             <TLCredit>50</TLCredit>
          </NomLine>   
         </NomHeader>
    </sage50Data>

XML API Tags for Sage 50 Entity 'NominalHeader'

Tag Name	Data Type	Description
Header:
THRef	Text 30 Head	Overide Heading Ref, thus causing a new transaction on change
THDate	Date Head	Overide Heading Date, thus causing a new transaction on change
Nominal Lines:
TLNomCode^	Text 8	Product Description. PostTrans stops importing after finding 5 consecutive blank cells. In Cell Searching values in table NomCodeNoDesc
TLExterRef	Text 30	External Referance set on each line
TLDepartment^	Integer	Department. Make sure the format of the cell is “General” else search may not work properly In Cell Searching values in table DeptCode
TLDetails	Text 60	Details
TLTaxCode^	Integer	Tax Code. Make sure the format of the cell is “General” else search may not work properly In Cell Searching values in table TaxCode
TLDebit^	Currency	Debit. Posttrans will ignore line if zero value in TLDebit and TLCredit Changes in this cell will recalc other cells. Delete ^ to disable this calculation.
TLCredit^	Currency	Credit. Posttrans will ignore line if zero value in TLDebit and TLCredit Changes in this cell will recalc other cells. Delete ^ to disable this calculation.
TLAmount^	Currency	Amount (used instead of Debit and Credit, thus +/- values in one column). Posttrans will ignore line if Zero Value in TLDebit and TLCredit Changes in this cell will recalc other cells. Delete ^ to disable this calculation.
TLTaxAmount	Currency	VAT Amount calculated based on Credit/Debit and Tax code on line
TLDonFund^	Integer	Charity Fund Number In Cell Searching values in table CharityCode

Req = Field is required EOF = End of file, Stop when no more values

Head A header tag can be used in header section, before row 30, of the transaction template. Or in the rows data of data, below row 30, of the template like a traditional CSV importer.

With data type Yes/No fields, if cell starts with 'y' or 'Y' is taken as TRUE

Where ^ denotes a In Cell Code Search, delete ^ at end of tag, to turn off code search

All Text fields are trimmed (spaces before) by default. Add ' to the end of the tag name to stop this.