Type Deriving Logic

The invoice type is determined based on the presence of a purchase order (PO) value:

• If the PO value exists, the invoice is classified as PO type.
• If the PO value is empty, the invoice is classified as Non-PO type.

Date Conversion Logic

Date formats from the invoice are converted to the ISO standard YYYY-MM-DD. Key points include:

• Supports various date formats such as “2nd Sep, 2022”, “02-Sep-2022”, and numeric formats like “09-02-2022”.
• Recognizes only MM-DD-YYYY numeric formats for conversion; DD-MM-YYYY is not converted if DD is less than 12.

Currency Conversion Logic

The system supports multiple locale currency formats, including US, European, and Indian number systems. It standardizes various currency representations by:

• Recognizing currency codes and symbols with or without spaces (e.g., “76 EUR”, “76€”, “EUR76”).
• Handling number formatting with commas, dots, or other separators for grouping and decimals.
• Determining invoice currency based on purchase order currency for PO invoices or legal entity local currency for Non-PO invoices, defaulting to system currency if necessary.

Unit Price Conversion Logic

Unit prices with currency symbols or codes are converted to a standardized numeric format, supporting locale-specific formats such as “1,00,025.10” or “$1,000,25.10”. This ensures consistent unit price values regardless of invoice origin.

Decimal Conversion Logic

The application interprets decimal and thousand separators based on locale conventions (e.g., European commas as decimals, dots as thousands). It converts values accordingly, but if only a single decimal separator is present, the value is set to empty to avoid incorrect conversions.

Reference Field Value Fetching Logic

The system populates key reference fields on the invoice by applying specific matching rules:

• Legal Entity: Determined from invoice billing address elements in hierarchical order (Bill to company, City, State, Country, Zip).
• Purchase Order: Extracted by cleaning prefixes and matching the remaining value to ERP purchase order numbers.
• Supplier: Matched against the Supplier table with exact or partial name matching combined with address details to identify the correct supplier.
• Country: Taken directly from the invoice or populated with ISO short or long country names if missing.
• Subtotal, Tax, Other Charges: Numeric values are grouped and converted based on decimal separator rules; negative amounts are identified including those indicated by brackets or trailing minus signs, triggering classification as Credit memo invoices.

Practical Benefits for ServiceNow Customers

This transformation logic enables ServiceNow customers to automate invoice data ingestion accurately, reducing manual corrections and errors. It supports diverse invoice formats and international standards, ensuring reliable processing across global operations. By leveraging this logic, customers can expect streamlined accounts payable workflows with enhanced data consistency and compliance.