Versions Compared

Old Version 61

changes.mady.by.user Min Zeng

Saved on

compared with

New Version 62

changes.mady.by.user Min Zeng

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Account SettingDescriptionShortcode MappingsExampleExample Shortcode
Exchange Rate Decimal PlacesNumber of decimal places in the GP exchange raten/a

Great Plains Account String Format

Account string built by Projector for GP. Typically this is in the form {0}-{1}.

There is some extended functionality with these shortcodes that allow you to splice off certain sections of characters. You use these features if you need to match a more complex Chart of Accounts structure.

Start at Character X

{0:2} - Place a colon and a number to start at a specific character. In this example the value would be everything from the third character in the cost center name onwards.

Start at Character X for Length L

{0:2,4} - Place a comma and a number for the length to get. In this example the value would be the first four characters after the third characters.


As a complex example, let's say our chart of accounts structure is:

 Department - Account - CostCenter (xx-xxxx-xx)

In this case, notice how the Account number is smushed between the Department and Cost Center. The Department and Cost Center values are both going to come from the {0} shortcode. We will use the string manipulators above to grab the portion that we need.

Our base format is:

{0}-{1}-{0}

We then grab the first three digits of the {0} shortcode to populate the department:

{0:0,3}-{1}-{0}

Finally, we grab the remaining characters in the {0} shortcode to populate the Cost Center.

{0:0,3}-{1}-{0:3}

US-4100{0}-{1}
Vendor Invoice Document Number FormatDocument number format for vendor invoices
  • {0} - PV number
  • {1} - Transaction number
  • {2} - VI number
  • {3} - VI reference number
PV00045-5001{0}-{1}
Unapproved to Pay Vendor Invoice Document NumberDocument number format for voided invoices
  • {0} - PV number
  • {1} - Transaction number
  • {2} - VI number
  • {3} - VI reference number
PV00045-5001V{0}-{1}V
Expense Report Document Number FormatDocument number for expense reports
  • {0} - PV number
  • {1} - Transaction number
  • {2} - ER number
PV00045-5001{0}-{1}
Unapproved to Pay Expense Report Document NumberVoided Expense Reports
  • {0} - PV number
  • {1} - Transaction number
  • {2} - ER number
PV00045-5001V{0}-{1}V
Great Plains A/P Transaction Description Field Format

When AP transaction is sent from Projector, include this information in the memo field.

  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "AP" - Hardcoded to this string
  • {2} - AP Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Payment Voucher #
  • {7} - Vendor Reference Invoice # - Found on a resource's profile for expense reports. Found on a vendor's profile for vendor invoices.on a payment voucher
  • {8} - Expense Document #
  • {17} - Expense Document Name
ER00123{17}
Great Plains A/R Transaction Description Field Format (client level invoices)

When an invoice at the client level is sent as an AR transaction from Projector, include this information in the memo field.

  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} - null

In addition client level invoices have access to these shortcodes

  • {9} - Client #
  • {10} - Client Name
INV00101{7}
Great Plains A/R Transaction Description Field Format (PO level invoices)

When an invoice at the PO level is sent as an AR transaction from Projector, include this information in the memo field.

Same as Client section except

  • {13} - Purchase order #
INV00101{7}
Great Plains A/R Transaction Description Field Format (engagement level invoices)

When an invoice at the engagement level is sent as an AR transaction from Projector, include this information in the memo field.

Same as Client section except

  • {11} - Engagement Code
  • {12} - Engagement Name
INV00101{7}
Great Plains A/R Transaction Description Field Format (project level invoices)

When an invoice at the project level is sent as an AR transaction from Projector, include this information in the memo field.

Same as Client section except

  • {11} - Engagement Code
  • {12} - Engagement Name
  • {14} - Project Code
  • {15} - Project Name
INV00101{7}
Great Plains G/L Transaction Description Field Format

When a GL batch is sent from Projector, include this information in the memo field.

Fields seven through fifteen are only available if you have the additional settings Transmit P&L detail in journal entries and Transmit reconciliation detail in journal entries turned on.

Those settings are typically off because it creates an enormous amount of data that needs to flow into QuickBooks.

  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "GL" - Hardcoded to this string
  • {2} - GL Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - GL Batch #
  • {7} - The description on a transmitted cost card or the description on a reconciliation item
  • {8} - The expense report number on a transmitted cost card (not populated for reconciliation items)
  • {9} - Client Number
  • {10} - Client Name
  • {11} - Engagement Code
  • {12} - Engagement Name
  • {13} - Resource Display Name
  • {14} - Project Code
  • {15} - Project Name
  • {16} - Payment Voucher # (only populated when you have reconciliation items)
PGJE#1234*P001023-001PGJE#{2}*{14}

...

Account SettingDescriptionShortcodesExampleExample Shortcode
QuickBooks A/P Transaction Memo Field FormatWhen AP transaction is sent from Projector, include this information in the memo field.
  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "AP" - Hardcoded to this string
  • {2} - AP Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Payment Voucher #
  • {7} - Vendor Reference Invoice # - Found on a resource's profile for expense reports. Found on a vendor's profile for vendor invoices.on a payment voucher
  • {8} - Expense Document #
Projector AP Txn#0000001234,2014-02,PVER00012 ;revcorp-tcs;Exp Doc #ER00042;Vendor Ref #64321Projector AP Txn#{2:D10},{0},{6}   ;{3};Exp Doc #{8};Vendor Ref #{7}
QuickBooks A/R Transaction Memo Field Format (client)When an invoice at the client level is sent as an AR transaction from Projector, include this information in the memo field.
  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} - null

In addition client level invoices have access to these shortcodes

  • {9} - Client #
  • {10} - Client Name
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;Acme Manufacturing (C0100)Projector AR Txn#{2:D10},{0},{6}    ;{3};{10} ({9})
QuickBooks A/R Transaction Memo Field Format (PO level invoices)When an invoice at the PO level is sent as an AR transaction  from Projector, include this information in the memo field.

Same as Client section except

  • {13} - Purchase order #
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;PO123456789Projector AR Txn#{2:D10},{0},{6}    ;{3};{13}
QuickBooks A/R Transaction Memo Field Format (engagement level invoices)When an invoice at the Engagement level is sent as an AR transaction  from Projector, include this information in the memo field.

Same as Client section except

  • {11} - Engagement Code
  • {12} - Engagement Name
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;EA Air Website (P001020)Projector AR Txn#{2:D10},{0},{6}    ;{3};{12} ({11})
QuickBooks A/R Transaction Memo Field Format (project level invoices)When an invoice at the Project level is sent as an AR transaction  from Projector, include this information in the memo field.

Same as Client section except

  • {11} - Engagement Code
  • {12} - Engagement Name
  • {14} - Project Code
  • {15} - Project Name
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;EA Air Website Support (P001020-002)Projector AR Txn#{2:D10},{0},{6}    ;{3};{15} ({14})
QuickBooks G/L Transaction Memo Field Format

When a GL batch is sent from Projector, include this information in the memo field.

Fields seven through fifteen are only available if you have the additional settings Transmit P&L detail in journal entries and Transmit reconciliation detail in journal entries turned on.

Those settings are typically off because it creates an enormous amount of data that needs to flow into QuickBooks.

  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "GL" - Hardcoded to this string
  • {2} - GL Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - GL Batch #
  • {7} - The description on a transmitted cost card or the description on a reconciliation item
  • {8} - The expense report number on a transmitted cost card (not populated for reconciliation items)
  • {9} - Client Number
  • {10} - Client Name
  • {11} - Engagement Code
  • {12} - Engagement Name
  • {13} - Resource Display Name
  • {14} - Project Code
  • {15} - Project Name
  • {16} - Payment Voucher # (only populated when you have reconciliation items)

Cost Card

Projector GL Txn#0000012345,2014-12,BATCH00124  ;revcorp-tcs;P001001-001;dinner with John Hentz to discuss plans;ER00005;;Debby Hill

Reconciliation Item

Projector GL Txn#0000012345,2014-12,BATCH00124  ;revcorp-tcs;P001001-001;dinner with John Hentz to discuss plans;;PV001234;Debby Hill

Projector GL Txn#{2:D10},{0},{6}  ;{3};{14};{7};{8};{16};{13}

...

Account SettingDescriptionShortcodesExampleExample Shortcode
Intacct A/P Transaction Memo Field FormatWhen AP transaction is sent from Projector, include this information in the memo field.
  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "AP" - Hardcoded to this string
  • {2} - AP Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Payment Voucher #
  • {7} - Vendor Reference Invoice # - Found on a resource's profile for expense reports. Found on a vendor's profile for vendor invoices.on a payment voucher
  • {8} - Expense Document #
Projector AP Txn#0000001234,2014-02,PVER00012 ;revcorp-tcs;Exp Doc #ER00042;Vendor Ref #64321Projector AP Txn#{2:D10},{0},{6}   ;{3};Exp Doc #{8};Vendor Ref #{7}
Intacct A/R Transaction Memo Field Format (client level invoices)When an invoice at the client level is sent as an AR transaction from Projector, include this information in the memo field.
  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} - null

In addition client level invoices have access to these shortcodes

  • {9} - Client #
  • {10} - Client Name
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;Acme Manufacturing (C0100)Projector AR Txn#{2:D10},{0},{6}    ;{3};{10} ({9})
Intacct A/R Transaction Memo Field Format (PO level invoices)When an invoice at the PO level is sent as an AR transaction  from Projector, include this information in the memo field.

Same as Client section except

  • {13} - Purchase order #
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;PO123456789Projector AR Txn#{2:D10},{0},{6}    ;{3};{13}
Intacct A/R Transaction Memo Field Format (engagement level invoices)When an invoice at the Engagement level is sent as an AR transaction  from Projector, include this information in the memo field.

Same as Client section except

  • {11} - Engagement Code
  • {12} - Engagement Name
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;EA Air Website (P001020)Projector AR Txn#{2:D10},{0},{6}    ;{3};{12} ({11})
Intacct A/R Transaction Memo Field Format (project level invoices)When an invoice at the Project level is sent as an AR transaction  from Projector, include this information in the memo field.

Same as Client section except

  • {11} - Engagement Code
  • {12} - Engagement Name
  • {14} - Project Code
  • {15} - Project Name
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;EA Air Website Support (P001020-002)Projector AR Txn#{2:D10},{0},{6}    ;{3};{15} ({14})
Intacct G/L Transaction Memo Field Format

Each individual GL transaction line includes a memo field. This setting determines what goes into that memo field.

Fields seven through fifteen are only available if you have the additional settings Transmit P&L detail in journal entries and Transmit reconciliation detail in journal entries turned on. Those settings are typically off because it creates an enormous amount of data that needs to flow into Intacct.

  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "GL" - Hardcoded to this string
  • {2} - GL Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - GL Batch #
  • {7} - The description on a transmitted cost card or the description on a reconciliation item
  • {8} - The expense report number on a transmitted cost card (not populated for reconciliation items)
  • {9} - Client Number
  • {10} - Client Name
  • {11} - Engagement Code
  • {12} - Engagement Name
  • {13} - Resource Display Name
  • {14} - Project Code
  • {15} - Project Name
  • {16} - Payment Voucher # (only populated when you have reconciliation items)

Cost Card

Projector GL Txn#0000012345,2014-12,BATCH00124  ;revcorp-tcs;P001001-001;dinner with John Hentz to discuss plans;ER00005;;Debby Hill

Reconciliation Item

Projector GL Txn#0000012345,2014-12,BATCH00124  ;revcorp-tcs;P001001-001;dinner with John Hentz to discuss plans;;PV001234;Debby Hill

Projector GL Txn#{2:D10},{0},{6}  ;{3};{14};{7};{8};{16};{13}
Intacct G/L Transaction Description Field Format

GL description fields are associated with a parent GL transaction. That parent may contain many GL line item transactions. This setting determines the description for the parent.

Fields seven through fifteen are only available if you have the additional settings Transmit P&L detail in journal entries and Transmit reconciliation detail in journal entries turned on. Those settings are typically off because it creates an enormous amount of data that needs to flow into Intacct.

  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "GL" - Hardcoded to this string
  • {2} - GL Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - GL Batch #
  • {7} - The description on a transmitted cost card or the description on a reconciliation item
  • {8} - The expense report number on a transmitted cost card (not populated for reconciliation items)
  • {9} - Client Number
  • {10} - Client Name
  • {11} - Engagement Code
  • {12} - Engagement Name
  • {13} - Resource Display Name
  • {14} - Project Code
  • {15} - Project Name
  • {16} - Payment Voucher # (only populated when you have reconciliation items)

Projector {1} Txn#{2:D10},{0},{6}  ;{3};;;;;
Intacct Journal ID for G/L TransactionsWhen browsing your GJE entries in Intacct, you can sort on transaction type, this value is what goes there. Useful for finding all GL transactions from Projector.There are no shortcodesPPSAGJEPPSAGJE
Intacct Payment Voucher Document Number FormatEach AP transaction must include a "Bill Number." This is where you define that bill number format.
  • {0} - Payment Voucher #
  • {1} - Transaction #
  • {2} - Vendor Invoice #
AMEX01 (PVVI00302){2} ({1})

...

You can change these values, but their formats were specifically chosen to make account reconciliations between Projector and Business Central faster. If you ever require our consulting team to go in and do an audit on your books, it may take longer if these standard settings are changed. If you do make changes, the information before the first semi-colon should try and stay a fixed width, for instance 80 characters. That is why we have padding spaces before the first semi-colon AND why we use a string formatter, {2:D10}, to force transaction numbers to be ten digits. Information after that semi-colon you can feel more free to edit. 

Image Removed Image Added

Account SettingDescriptionShortcodesExampleExample Shortcode
BC Tenant NameName of the Business Central Tenant to connect to.  Ask the development team for details please.

NULL
BC
Dimension NamesWhen mapping to dimensions, this allows the user to specify, positionally, the name of each dimension. 
Environment NameThe name of a Business Central Sandbox environment.  Leave it blank if integrating with the real Business Central instance. 


BC API Version NumberThe API version number used in the transaction synchronization.  Ask the development team for details please. 


BC Cost Center Mapped Dimension NamesWhen mapping to dimensions, this allows the user to specify, positionally, the name of each dimension.  Enter the names of the configured dimensions, separated by
pipe characters
the designated delimiter, in the same order the dimension values are specified in
in
cost center mappings.  Matching dimension names and value lists need to exist in Business Central for the synchronization to succeed. 

NULL
BC
Tax CodeProjector will use this as the tax code in all transactions sent over to Business Central. Tax should be set up with a 0% rate, as Projector handles taxes as separate items.PPSATAXBC A/P Transaction Description Field FormatDescription field format for payment vouchers..
Dimension DelimiterThe delimiter used to decode the cost center dimension string, A/P, A/R and G/L line dimention string 
|
Set Mapped Dimesnions at A/P Invoice LevelIf set to true, A/P transaction's GL line's cost center dimension will be set at the A/P invoice level.  other wise, A/P line's cost center dimension is set at the line level only. 


Set Mapped Dimensions at A/R Invoice LevelIf set to true, A/R transaction's GL line's cost center dimension will be set at the A/R invoice level.  other wise, A/R line's cost center dimension is set at the line level only. 


BC Tax CodeProjector will use this as the tax code in all transactions sent over to Business Central. Tax should be set up with a 0% rate, as Projector handles taxes as separate items.

PPSATAX
BC A/P Transaction Description Field FormatDescription field format for payment vouchers..
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "AP" - Hardcoded to this string
  • {2} - AP Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Payment Voucher #
  • {7} - Vendor Invoice # on a payment voucher
  • {8} - Expense Document #

Projector {1} Txn#{2:D10},{0},{6}   ;{3};Exp Doc #{8};Vendor Ref #{7}
BC A/P Invoice Line Dimension MappingsAdditional A/P invoice line dimension delimited using BC Dimension Delimiter. Matching dimension names and value lists need to exist in Business Central for the synchronization to succeed. See above 
PVNo={6}|VendNo={7}
BC A/R Transaction Description Field Format (client level invoices)Description field format for client level invoices. The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "
AP
  • AR" - Hardcoded to this string
  • {2} -
AP
  • AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} -
Payment Voucher {8} - Expense Document #
Vendor Reference # - Found on a resource's profile for expense reports. Found on a vendor's profile for vendor invoices.
  • Invoice Name
  • {8} = Client Number
  • {9} = Client Name
  • {10} = Purchase Order Number
  • {11} = Engagement Code
  • {12} = Engagement Name
  • {13} = Project Code
  • {14} = Project Name

Projector {1} Txn#{2:D10},{0},{6}
  
    ;{3};
Exp Doc #
{
8};Vendor Ref #{7}
10} ({9})
BC A/R Transaction Description Field Format (
client
PO level invoices)Description field format for
client
purchase order level invoices.
The
 The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} = Client Number
  • {9} = Client Name
  • {10} = Purchase Order Number
  • {11} = Engagement Code
  • {12} = Engagement Name
  • {13} = Project Code
  • {14} = Project Name

Projector {1} Txn#{2:D10},{0},{6}    ;{3};{
10} ({9
13}
)
BC A/R Transaction Description Field Format (
PO
engagement level invoices)Description field format for
purchase order
engagement level invoices. The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} = Client Number
  • {9} = Client Name
  • {10} = Purchase Order Number
  • {11} = Engagement Code
  • {12} = Engagement Name
  • {13} = Project Code
  • {14} = Project Name

Projector {1} Txn#{2:D10},{0},{6}    ;{3};{12} ({
13
11})
BC A/R Transaction Description Field Format (
engagement
project level invoices)Description field format for
engagement
project level invoices.
 The
  The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} = Client Number
  • {9} = Client Name
  • {10} = Purchase Order Number
  • {11} = Engagement Code
  • {12} = Engagement Name
  • {13} = Project Code
  • {14} = Project Name

Projector {1} Txn#{2:D10},{0},{6}    ;{3};{12} ({11})
BC
A/R Transaction Description Field Format (project level invoices)Description field format for project level invoices.  The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} = Client Number
  • {9} = Client Name
  • {10} = Purchase Order Number
  • {11} = Engagement Code
  • {12} = Engagement Name
  • {13} = Project Code
  • {14} = Project Name
Projector {1} Txn#{2:D10},{0},{6}    ;{3};{12} ({11})
G/L Journal IdentifierIf specified, lines will be added to an existing journal, identified by this value. Otherwise, a new journal is created and lines added to the new entry.

GL-10001
BC A/R Invoice Line Dimension MappingsAdditional A/R invoice line dimension delimited using BC Dimension Delimiter. Matching dimension names and value lists need to exist in Business Central for the synchronization to succeed. See code for BC A/R Transaction Description Field Format (project level invoices)
InvNo={6}|ClinNo={8}
BC G/L Code Field FormatThis field defines the journal code when Projector is creating journals. It supports two placeholders: {0} – Transaction Batch Number and {1} – GL Transaction Number. Default value is ‘{1}’.
  • {0} – Transaction Batch Number
  • {1} – GL Transaction Number


BC G/L Comment Field FormatComment field format for journal entries. 
  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "GL" - Hardcoded to this string
  • {2} - GL Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - GL Batch #
  • {7} - The description on a transmitted cost card or the description on a reconciliation item
  • {8} - The expense report number on a transmitted cost card (not populated for reconciliation items)
  • {9} - Client Number
  • {10} - Client Name
  • {11} - Engagement Code
  • {12} - Engagement Name
  • {13} - Resource Display Name
  • {14} - Project Code
  • {15} - Project Name
  • {16} - Payment Voucher # (only populated when you have reconciliation items)

PPSAGJE
BC G/L Display Name Field FormatDisplay name field format for journal entries. 
  • {0} = Company Number
  • {1} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable

C{0}-AP{1}
BC G/L Transaction Description Field FormatDescription field format for journal entries. The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "GL" - Hardcoded to this string
  • {2} - GL Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - GL Batch #
  • {7} - The description on a transmitted cost card or the description on a reconciliation item
  • {8} - The expense report number on a transmitted cost card (not populated for reconciliation items)
  • {9} - Client Number
  • {10} - Client Name
  • {11} - Engagement Code
  • {12} - Engagement Name
  • {13} - Resource Display Name
  • {14} - Project Code
  • {15} - Project Name
  • {16} - Payment Voucher # (only populated when you have reconciliation items)

Projector {1} Txn#{2:D10},{0},{6}  ;{3};{14};{7};{8};{16};{13}
BC G/L Transaction Document Number Field FormatDocument Number field format for journal entries. 
DOC{1}
BC G/L Journal Line Dimension MappingsAdditional G/L invoice line dimension delimited using BC Dimension Delimiter. Matching dimension names and value lists need to exist in Business Central for the synchronization to succeed. 


Create Vendors in BC AutomaticallyTurn this setting on to have Projector create vendors in Business Central automatically as necessary.When Projector tries to send over an AP transaction and the vendor does not already exist in Business Central, Projector will attempt to create the vendor in BC. Note there is no ongoing synching of vendors, only initial creation.
0
Create Customers in BC AutomaticallyTurn this setting on to have Projector create customers in Business Central automatically as necessary.When Projector tries to send over an AR transaction and the customer does not already exist in Business Central, Projector will attempt to create the customer in BC. Note there is no ongoing synching of customers, only initial creation.
0



Web Services Accounting Interface

...

Account SettingDescriptionShortcodesExampleExample Shortcode
Web Services A/P Transaction Memo Field FormatWhen AP transaction is sent from Projector, include this information in the memo field.
  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "AP" - Hardcoded to this string
  • {2} - AP Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Payment Voucher #
  • {7} - Vendor Reference Invoice # - Found on a resource's profile for expense reports. Found on a vendor's profile for vendor invoices.on a payment voucher
  • {8} - Expense Document #
Projector AP Txn#0000001234,2014-02,PVER00012 ;revcorp-tcs;Exp Doc #ER00042;Vendor Ref #64321Projector AP Txn#{2:D10},{0},{6}   ;{3};Exp Doc #{8};Vendor Ref #{7}
Web Services A/R Transaction Memo Field Format (client level invoices)When an invoice at the client level is sent as an AR transaction from Projector, include this information in the memo field.
  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} - null

In addition client level invoices have access to these shortcodes

  • {9} - Client #
  • {10} - Client Name
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;Acme Manufacturing (C0100)Projector AR Txn#{2:D10},{0},{6}    ;{3};{10} ({9})
Web Services A/R Transaction Memo Field Format (PO level invoices)When an invoice at the PO level is sent as an AR transaction  from Projector, include this information in the memo field.

Same as Client section except

  • {13} - Purchase order #
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;PO123456789Projector AR Txn#{2:D10},{0},{6}    ;{3};{13}
Web Services A/R Transaction Memo Field Format (engagement level invoices)When an invoice at the Engagement level is sent as an AR transaction  from Projector, include this information in the memo field.

Same as Client section except

  • {11} - Engagement Code
  • {12} - Engagement Name
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;EA Air Website (P001020)Projector AR Txn#{2:D10},{0},{6}    ;{3};{12} ({11})
Web ServicesA/R Transaction Memo Field Format (project level invoices)When an invoice at the Project level is sent as an AR transaction  from Projector, include this information in the memo field.

Same as Client section except

  • {11} - Engagement Code
  • {12} - Engagement Name
  • {14} - Project Code
  • {15} - Project Name
Projector AR Txn#0000012345,2014-10,INV00009    ;revcorp-tcs;EA Air Website Support (P001020-002)Projector AR Txn#{2:D10},{0},{6}    ;{3};{15} ({14})
Web Services Journal ID for G/L TransactionsWhen browsing your GJE entries in Intacct, you can sort on transaction type, this value is what goes there. Useful for finding all GL transactions from Projector.There are no shortcodesPPSAGJEPPSAGJE
Web Services Payment Voucher Document Number FormatEach AP transaction must include a "Bill Number." This is where you define that bill number format.
  • {0} - Payment Voucher #
  • {1} - Transaction #
  • {2} - Vendor Invoice #
AMEX01 (PVVI00302){2} ({1})

...