Skip to main content
Skip table of contents

SI.WRITEBACKJOURNAL

Overview

The SI.WRITEBACKJOURNAL function defines a single journal transaction line to be uploaded to Sage Intacct.

For a short overview of the Journal Writeback process see: Journal Writeback (Sage Intacct).

Performing writeback (i.e., Creating entities through the Sage Intacct application programming interface) requires the access rights associated with a Full User.

Employee-type users in Sage Intacct would not be able to successfully perform a writeback.


The SI.WRITEBACKJOURNAL function is used to *create* journal transactions. It cannot be used to modify/update existing transactions.

In order to separate multiple Writeback functions into groups and execute them in batches, you can use the WRITEBACKCOMMIT function.

Syntax

CODE 
=SI.WRITEBACKJOURNAL(ConnectionName,Journal,PostingDate,ReverseDate,JournalDescription,ReferenceNumber,ShouldPost,AdditionalBatchSettings,Account,Debit,Credit,LineCurrencySettings,Memo,Location,LineAllocationSettings,Dimensions,UserDefinedDimensions,Billable,TaxEntry,BatchNumberOutput,ShouldOpenAfterUpload)

Arguments

The SI. WRITEBACKJOURNAL function uses the following Header and Line arguments:

Header Info

Argument

Required/Optional

Description

ConnectionName

Required

The name of the connection as configured in the Connection Manager

Journal

Required

GL journal symbol. This determines the type of journal entry as visible in the UI, for example, Regular, Adjustment, User-defined, Statistical, GAAP, Tax, and so forth

PostingDate

Required

The transaction date in format mm/dd/yyy

ReverseDate

Optional

Reverse date in format mm/dd/yyyy. Must be greater than PostingDate

JournalDescription

Required

Journal description for the transaction

ReferenceNumber

Optional

Reference number of the transaction

ShouldPost

Required

TRUE or FALSE. Determines whether or not the transaction should be automatically posted once it is created

AdditionalBatchSettings

Optional

A two-column array of key and value pairs for defining the settings

The AdditionalBatchSettings argument is a two-column array of key+value pairs, where the "key" is a forgiving name of the respective setting from the API description:

  1. [WritebackLocationId] - allows you to specify explicitly under which entity the journal transaction should be created. If left empty, Velixo applies a smart entity scoping algorithm:

    • if you aren't using any entity-private dimension values, Velixo will create the transaction at the top level.

    • if you use an entity-private dimension value, Velixo will create the transaction in the same entity as the entity-private dimension values.

  2. [BaseLocationId] - for multi-entity transactions, allows you to specify the source entity ID (do not confuse with Target entity ID). This field is required if multi-entity is enabled and entries do not balance by entity

  3. [TaxImplications] - Tax implications. Use None, Inbound for purchase tax, or Outbound for sales tax

  4. [TaxSolutionId] - Tax solution name, such as United Kingdom - VAT or Australia - GST. Required only if the company is configured for multiple tax jurisdictions and the transaction is occurring at the top level of the company

  5. [VatVendorId] - Vendor ID when tax implications is set to Inbound for tax on purchases

  6. [VatCustomerId] - Customer ID when tax implications is set to Outbound for tax on sales

  7. [VatContactId] - Contact name for the customer SHIPTO contact for sales journals or the vendor ID for the vendor PAYTO contact for purchase journals

  8. [HistoryComment] - Comment added to history for this transaction

  9. [TransactionSource] - The source of the entry

  10. [CustomFieldName1] - Custom field names and values as defined for this object

  11. [CustomFieldName2]

  12. [CustomFieldName...]


Note that anything that is not recognized as a predefined field, is treated as the "Custom field name" from the API description.

Example:

(this example sets values for VatVendorID, VatCustomerID, and VatContactID)

Line Info

Account

Required

The GL account number for the transaction

Debit

Optional (must be left blank if Credit amount is specified)

The Debit amount to be sent to the GL Account

Credit

Optional (must be left blank if Debit amount is specified)

The Credit amount to be sent to the GL Account

LineCurrencySettings

Optional

The currency code to be used for the transaction

Memo

Optional

A memo to be included in the transaction

Location

Optional

(Required if muti-entity is enabled)

ID code for the Sage Intacct location to be used for the transaction

The LineAllocationSettings argument cannot be used at the same time as Location

LineAllocationSettings

Optional

Allocation ID

The LineAllocationSettings argument can be:

  • The Allocation ID or

  • A two-dimensional Excel range where the first row contains the name of a predefined analytical dimension (e.g. department, customer, project) and the following rows contain the respective values for that dimension. The last value must be the split transaction amount, and all split transactions amounts must sum up to either the credit or debit value.

    When the Allocation argument is used (either via Allocation ID or a a two-dimensional array), the Dimensions, UserDefinedDimensions or Location arguments cannot be used. When using allocation, predefined dimension values must be part of the allocation.


The LineAllocationSettings argument cannot be used at the same time as Dimensions, UserDefinedDimensions or Location

Dimensions

Optional

A two-column (or two-row) Excel range, where the first column/row contains the name of a predefined analytical dimension (e.g. department, customer, project etc.), and the second column/row contains the semicolon-separated list of values or that dimension.

For user-defined dimensions, use the UserDefinedDimensions argument

The LineAllocationSettings argument cannot be used at the same time as Dimensions

UserDefinedDimensions

Optional

A two-column (or two-row) Excel range, where the first column/row contains the name of a user-defined analytical dimension, and the second column/row contains the respective value (or a semicolon-separated list of values) for that dimension.

For predefined analytical dimensions like customer, project etc., use the Dimensions argument

The LineAllocationSettings argument cannot be used at the same time as UserDefinedDimensions

Billable

Optional

TRUE or FALSE (default)

Applies to project-related transactions and sets whether or not the transaction is billable.

TaxEntry

Required for AU, GB, ZA only

A two-column Excel range, where the first column contains text specifying the tax rate (as specified via the unique ID of a tax detail) and the second column contains a currency value denoting the value of the tax.

BatchNumberOuput

Optional

The Excel cell to receive the batch code number of the batch that is created

ShouldOpenAfterUpload

Optional

TRUE or FALSE (default).

Indicates whether or Sage Intacct should be opened to the batch following its creation

Examples

Example 1

CODE 
=SI.WRITEBACKJOURNAL("Sage","GJ","12/31/2019",,"Liability Insurance Accrual for December 2019",,False,,"60330",,"1322.41","USD",,"100",,,,,,I9,TRUE)


Expanded:

CODE 
=SI.WRITEBACKJOURNAL("Sage","GJ","12/31/2019",,"Liability Insurance Accrual for December 2019",,False,,"60330",,"1322.41","USD",,"100",,,,,,I9,TRUE)


Description

Creates a transaction in the "GJ" journal. The transaction:

  • will be dated "12/31/2019"

  • does not have a reversal date

  • has the description of "Liability Insurance Accrual for December 2019"

  • should not be automatically posted

  • will be created for GL account #60330

  • will have the credit amount of 1,322.41 US dollars

  • will be created in location 100

In addition:

  • the number for the created batch number will be recorded in cell I9

  • Sage Intacct will automatically be opened to the batch immediately after it is created

using cell references:

CODE 
=SI.WRITEBACKJOURNAL($E$2,"GJ",$E$5,$I$11,$E$6,,IF($I$10="Yes",TRUE,FALSE),,$E$12,,
J17,$I$4,,$B17,,,,,,I9,TRUE)

Here you can see an example where the cells contain the data for the function in cell K16:


Example 2

Using the TaxEntry and AdditionalBatchSettings arguments:

For Credit transactions:

CODE 
=SI.WRITEBACKJOURNAL("Sage", "GJ", "12/31/2019", , "Liability Insurance Accrual for November 2019", , FALSE, {"TaxImplications","Outbound";"TaxSolutionID","United Kingdom - VAT";"VatCustomerID","10052"}, "60330", , 467.75, "USD", , "500", , , , , , I9, TRUE)


Expanded:

CODE 
=SI.WRITEBACKJOURNAL("Sage,"GJ","12/31/2019",,"Liability Insurance Accrual for November 2019",,FALSE,{"TaxImplications","Outbound";"TaxSolutionID","United Kingdom - VAT";"VatCustomerID","10052"},"60330",,467.75,"USD",,"500",,,,,,I9,TRUE)

For Debit transactions:

CODE 
=SI.WRITEBACKJOURNAL("Sage", "GJ", "12/31/2019", , "Liability Insurance Accrual for November 2019", , FALSE, {"TaxImplications","Outbound";"TaxSolutionID","United Kingdom - VAT";"VatCustomerID","10052"}, "20330", 1,403.25, , "USD", , "500", , , , , {"UK Sale Goods Reduced Rate","89.2"}, I9, TRUE)


Expanded:

CODE 
=SI.WRITEBACKJOURNAL("Sage","GJ","12/31/2019",,"Liability Insurance Accrual for November 2019",,FALSE,{"TaxImplications","Outbound";"TaxSolutionID","United Kingdom - VAT";"VatCustomerID","10052"}, "20330",1,403.25,,"USD",,"500",,,,,{"UK Sale Goods Reduced Rate","89.2"},I9,TRUE)

Description

Creates a transaction in the "GJ" journal. The transaction:

  • will be dated "12/31/2019"

  • does not have a reversal date

  • has the description of "Liability Insurance Accrual for December 2019"

  • should not be automatically posted

  • with Tax implications = Outbound taxes for sales, Customer = 10052, Tax solution = United Kingdom - VAT.

  • 60330 GL account will be credited with the amount of 467.75 USD

  • 20330 GL account will be debited with the amount of 1,403.25 USD, including tax entry with "UK Sale Goods Reduced Rate" description and 89.20 USD amount

  • will be created in location 500


In addition:

  • The number for the created batch number will be recorded in cell I9

  • Sage Intacct will automatically be opened to the batch immediately after it is created


Here is the created journal entry in Sage Intacct:

In Excel, the transaction number from the journal entry has been recorded in cell I9 and the line status has been updated to Line uploaded.

Example 3

Using the LineAllocationSettings argument to provide an Allocation ID.

For Debit transactions:

CODE 
=SI.WRITEBACKJOURNAL("Sage", "GJ", "06/06/2025", , "Sample transaction 3", , FALSE,, "10000", 2000, , "USD", , , LOC_STD_SPLIT, , , , , , TRUE)

CODE 
=SI.WRITEBACKJOURNAL("Sage","GJ","12/31/2019",,"Sample transaction 3",,FALSE,,
"10000",1000,,"USD",,,LOC_STD_SPLIT,,,,,H9,TRUE)


For Credit transactions:

CODE 
=SI.WRITEBACKJOURNAL("Sage", "GJ", "06/06/2025", , "Sample transaction 3", , FALSE,, "10000", , 1200, "USD", , , LOC_STD_SPLIT, , , , , , TRUE)

CODE 
=SI.WRITEBACKJOURNAL("Sage","GJ","12/31/2019",,"Sample transaction 3",,FALSE,,
"10000",,2000,"USD",,,LOC_STD_SPLIT,,,,,H9,TRUE)

Description

Creates a transaction in the "GJ" journal. The transaction:

  • will be dated "06/06/2025"

  • does not have a reversal date

  • has the description of "Sample transaction 3"

  • should not be automatically posted

  • without tax implications.

  • 10000 GL account will be credited with the amount of 1000 USD

  • 10000 GL account will be debited with the amount of 1200 USD

  • will be created according to Allocation ID LOC_STD_SPLIT, which splits the value of transactions by percentage to three locations:


In addition:

  • The number for the created batch number will be recorded in cell H9

  • Sage Intacct will automatically be opened to the batch immediately after it is created

The formulas above result in the following entry in Sage Intacct:

Where the amounts are split according to the selected Allocation:

image-20250904-062454.png

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close