Versions Compared

Version Old Version 1 New Version 2
Changes made by

Lou Dizon

Lou Dizon

Saved on

Key

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

INFlow determines whether account is One World and Non-One World. If it’s the latter, all subsidiary parameters are ignored.

Vendor Field

Field Value Taken From

{expenseaccount}

[STA] EFlow preferences à {custrecord_sta_einv_pref_vendorexpacc}

{companyname}

Invoice|AccountingSupplierParty|Party|PartyName|Name à

InvoicerName1

 

{currency}

Invoice|DocumentCurrencyCode à

CurrencyUnit

 

{vatregno}

Invoice|AccountingSupplierParty|Party|PartyIdentification>VAT|ID à

InvoicerVATNumber

 

{terms}

Keep it blank if there are no matching payment terms in NetSuite list

Invoice|PaymentTerms|Note à

TermsOfPaymentFreeText

 

{custentity_sta_einv_businessid}

 

Invoice|AccountingSupplierParty|Party|PartyIdentification|ID à

InvoicerTIN

 

{custentity_sta_einv_networkid}

 

Invoice|AccountingSupplierParty|Party|EndpointID

SenderPeppolIdentifier

 

{custrecord_psg_ei_inbound_vendor}

If this value is blank upon creating the bill, set the default E-document package value to REST – Staria Integration on the Vendor record.

 

 

custentity_edoc_ws_id

 

Vendor Web-Service ID – VAT ID or Business ID

custentity_edoc_ws_sender

 

Set the employee which is assigned

Vendor Address fields

Default Billing

Yes (hardcoded)

Label

Billing (hardcoded)

{addr1}

Invoice|AccountingSupplierParty|Party|PostalAddress|StreetName à

InvoicerLocalAddress1

 

{addr2}

Invoice|AccountingSupplierParty|Party|PostalAddress|AdditionalStreetName à

InvoicerLocalAddress2

 

{city}

Invoice|AccountingSupplierParty|Party|PostalAddress|CityName à

InvoicerPostOffice

 

{zip}

Invoice|AccountingSupplierParty|Party|PostalAddress|PostalZone à

InvoicerPostalCode

 

{state}

Invoice|AccountingSupplierParty|Party|PostalAddress|CountrySubentity à

InvoicerCountryArea

 

{country}

Invoice|AccountingSupplierParty|Party|PostalAddress|Country|IdentificationCode à

InvoicerCountry

 

Vendor Contact fields

{entityid}

Invoice|AccountingSupplierParty|Party|Contact|Name à

InvoicerContactPersonName

 

{phone}

Invoice|AccountingSupplierParty|Party|Contact|Telephone à

InvoicerContactPersonTelephoneNumber

 

{email}

Invoice|AccountingSupplierParty|Party|Contact|ElectronicMail à

InvoicerContactPersonEmailAddress

 

Bank Payment Details fields

Create a new record Entity Bank Details {customrecord_2663_entity_bank_details}.

NOTE:

  • if both the LocalAccountNumber and IBANAccountNumber are present in xml, then Entity Bank Details with IBANAccountNumber will be of Secondary (ID=2) Entity Bank Details type

  • Before creating an Entity Bank Details record, check for existing entity bank details, according to IBAN and BBAN:

    • Check whether PayeeFinancialAccount for IBAN in XML is already existing on any of the Entity Bank Payment Details against that Vendor, in {custrecord_2663_entity_iban} fields.

    • Check whether PayeeFinancialAccount for BBAN in XML is already existing on any of the Entity Bank Payment Details against that Vendor, in {custrecord_2663_entity_bban} fields. If yes, then skip creating the record.

 NOTE:

  • If “Do not create new vendor bank details if does not match current” {custrecord_sta_einv_pref_newbankacc} is checked in INFlow Preferences record, do not create new entity bank details if the current set of bank details do not match those in the incoming file.

    • In this case, set “Vendor Details do not match” {custbody_sta_inflow_bankacc_nomatch} field value with the following details:

      • WARNING: Existing vendor bank details do not match those in the incoming file:

      • NEW BANK ACCOUNT: XXX

      • NEW SWIFT/BIC: YYY

      • The new details were NOT created

  • If “Do not create new vendor bank details if does not match current” {custrecord_sta_einv_pref_newbankacc} is NOT checked in INFlow Preferences record, then create new entity bank details if the current set of bank details do not match those in the incoming file and set “Vendor Details do not match” {custbody_sta_inflow_bankacc_nomatch} field value with the following details:

    • WARNING: NEW BANK ACCOUNT DETAILS WERE CREATED, as existing vendor bank details did not match those in the incoming file:

    • NEW BANK ACCOUNT: XXX

    • NEW SWIFT/BIC: YYY

  • If “Do not create new vendor bank details if do not match current” {custrecord_sta_einv_pref_newbankacc} in INFlow Preferences is marked to YES, AND, the entity bank payment details in the incoming file are not found among the existing set of entity bank details, then:

    • DO NOT create a new set entity bank account details

    • On the bill, in “Vendor Bank Details do not match” {custbody_sta_inflow_bankacc_nomatch} field set the following values with hardcoded labels:

      • NEW ACCOUNT NO: xxxxxxx

      • NEW BIC/SWIFT: yyyyyy

For the below set of fields coming from UBL message:

 

If PaymentChannelCode = BBAN, as per example below:

 

<cac:PaymentMeans>

<cbc:PaymentMeansCode>31</cbc:PaymentMeansCode>

<cbc:PaymentDueDate>2013-07-20</cbc:PaymentDueDate>

<cbc:PaymentChannelCode>BBAN</cbc:PaymentChannelCode>

<cbc:PaymentID>0003434323213231</cbc:PaymentID>

<cac:PayeeFinancialAccount>

<cbc:ID>011117947</cbc:ID>

<cac:FinancialInstitutionBranch>

<cac:FinancialInstitution>

<cbc:ID>DNBANOKK</cbc:ID>

</cac:FinancialInstitution>

</cac:FinancialInstitutionBranch>

</cac:PayeeFinancialAccount>

</cac:PaymentMeans>

 

Then domestic payment template has to be fetched, as listed below

{name}

[Subsidiary VAT ID] [BBAN]

{custrecord_2663_entity_bank_type}

 

Primary (ID=1)

{custpage_2663_entity_file_format}

 

[STA] INFlow preferences à {custrecord_sta_einv_pref_paymdom}

{custrecord_2663_entity_bban}

 

Invoice|PaymentMeans|PayeeFinancialAccount|ID à

LocalAccountNumber

{custrecord_2663_entity_bic}

 

Invoice|PaymentMeans|PayeeFinancialAccount|FinancialInstitutionBranch|FinancialInstitution|ID|@schemeURI à

SWIFTCode

For the below set of fields coming from UBL message:

 

If PaymentChannelCode = IBAN, as per example below:

 

<cac:PaymentMeans>

<cbc:PaymentMeansCode>31</cbc:PaymentMeansCode>

<cbc:PaymentDueDate>2013-07-20</cbc:PaymentDueDate>

<cbc:PaymentChannelCode>IBAN</cbc:PaymentChannelCode>

<cbc:PaymentID>0003434323213231</cbc:PaymentID>

<cac:PayeeFinancialAccount>

<cbc:ID>NO098011117947</cbc:ID>

<cac:FinancialInstitutionBranch>

<cac:FinancialInstitution>

<cbc:ID>DNBANOKK</cbc:ID>

</cac:FinancialInstitution>

</cac:FinancialInstitutionBranch>

</cac:PayeeFinancialAccount>

</cac:PaymentMeans>

 

Then foreign payment template has to be fetched, as listed below

{name}

[Subsidiary VAT ID] [IBAN]

{custrecord_2663_entity_bank_type}

Primary (ID=1)

{custpage_2663_entity_file_format}

[STA] eFlow preferences à {custrecord_sta_einv_pref_paymfor}

{custrecord_2663_entity_iban}

Invoice|PaymentMeans|PayeeFinancialAccount|ID à

IBANAccountNumber

{custrecord_2663_customer_code}

When subsidiary’s country is DK, and the Vendor’s country is DK, then PaymentID should consist of the following characters:

<cac:PaymentMeans>

<cbc:PaymentMeansCode/>

<cbc:PaymentDueDate>2019-01-29</cbc:PaymentDueDate>

<cbc:PaymentChannelCode>IBAN</cbc:PaymentChannelCode>

<cbc:PaymentID>+71<000000001590108+87700836<</cbc:PaymentID>

 

+71<000000030341903+83473657<

Take the value between + and < signs (last numeric part) and set it in the {custrecord_2663_customer_code} field, on the same Entity Bank Details record created for IBAN/BBAN

{custrecord_2663_entity_bic}

 

Invoice|PaymentMeans|PayeeFinancialAccount|FinancialInstitutionBranch|FinancialInstitution|ID à

SWIFTCode