The PayPal integration guide does not document a way to map PayPal invoice lines to Acumatica Inventory IDs, stock items, or non-stock items. Its documented workflow creates a PayPal invoice from an Acumatica sales order, accounts receivable invoice, or payment amount and then tracks the resulting payment at the document and application level.
The Biz-Tech Services PayPal Acumatica Connector sends payment requests and stores PayPal invoice identifiers, URLs, statuses, transaction IDs, refund IDs, and paid amounts. The source does not name a SKU, Inventory ID, item class, item alias, or product cross-reference field. Item mapping therefore remains outside the documented PayPal customization workflow.
What the PayPal Connector Sends from Acumatica
The Biz-Tech Services Acumatica PayPal Connector creates a PayPal payment request from one of three Acumatica entry points. A user can start from Sales Orders, from an Invoice, or from Payments and Applications. All three paths create or use an AR Payment, send a PayPal invoice to the customer’s email, and place the payment on Hold with a Sent status.
From Sales Orders, Create Payment reads the order total, currency, and customer details. After Cash Account and Payment Reference are supplied, Request PayPal Payment creates an AR Payment linked to the order and stores PayPal Invoice ID, Invoice URL, and Invoice Number on the payment.
From the documented Invoice workflow, Request PayPal Payment creates a payment pre-applied to the invoice. The PayPal invoice amount matches the outstanding balance. The guide does not state that Acumatica invoice lines are copied, matched, or recreated as PayPal invoice lines.
PayPal Invoice Line Mapping at a Glance
The source supports the following conclusions about the boundary between item records and PayPal payment requests.
1. Sales Orders can supply order total, currency, and customer details to the payment request
2. An accounts receivable invoice can supply its outstanding balance to the PayPal invoice amount
3. A standalone payment can supply a customer, PayPal payment method, email, amount, and optional description
4. Orders to Apply and Documents to Apply can associate a payment with a Sales Order or Invoice
5. PayPal fields are stored on the AR Payment and related ARAdjust and SOAdjust application records
6. No documented field maps a PayPal line description or product code to an Acumatica item
Sales Orders Supply Totals Rather Than Documented Item Mappings
The Sales Order path starts on Sales Orders. Create Payment reads the order total, currency, and customer details, and the resulting AR Payment remains accessible from the order’s Payments tab. The source describes the payment link to the order, not a line-by-line link to inventory records.
No PayPal line-item table, Inventory ID field, quantity field, unit price field, or product identifier is listed in this workflow. The documentation also does not say whether the customer sees one summarized PayPal invoice line or several lines. Any such behavior would need confirmation outside the supplied guide.
The payment application preserves a document relationship, but a document relationship is not an item cross-reference. The source does not provide evidence that changing an Acumatica sales order line changes an already sent PayPal invoice or that PayPal can update an inventory item.
AR Invoices Supply the Outstanding Balance
The Invoice path is designed for billing that has already been posted. Request PayPal Payment creates a payment pre-applied to the invoice, sends the PayPal invoice, and puts the payment on Hold. The source states that the PayPal amount matches the outstanding balance on the AR invoice.
Outstanding balance is the only invoice-content rule documented for this path. The guide does not mention invoice-line descriptions, Inventory IDs, quantities, item classes, tax categories by line, discounts by line, or line-level references in the PayPal request.
The Payment Method ID becomes locked once an invoice has been sent. That rule protects the PayPal payment method assignment; it is not an item-mapping lock or a line validation rule.
Standalone Payments Have No Required Item Context
Payments and Applications supports a standalone payment, such as a deposit that is not tied to a specific document. The user selects the customer and PayPal payment method, reviews PayPal Customer Email, enters the payment amount and an optional description, and sends the request.
A payment can optionally be applied to a Sales Order or Invoice through Orders to Apply or Documents to Apply. The source does not require an Inventory ID or item line for a standalone request. This confirms that the documented PayPal process operates at the payment and document level.
The optional description is not defined as a SKU, alias, inventory description, or matching key. The guide provides no rule for using it to identify an Acumatica item.
Cross References Aliases and Unmapped Items Are Not Documented
The Biz-Tech Services PayPal Acumatica Integration documentation contains no item cross-reference screen, alias table, SKU lookup, Inventory ID field, product-code mapping, item-class default, or unmapped-product queue. It does not describe any record that pairs a PayPal value with an Acumatica item.
No behavior is defined for an unknown PayPal product, duplicate product code, blank item value, different letter case, leading zeros, stock versus non-stock items, or multiple external aliases for one local item. The source also does not describe creating inventory records from PayPal data.
The only related line records named by the guide are ARAdjust and SOAdjust. The PayPal custom fields are available on those applied-to lines so payment status information remains consistent across related records. The guide does not identify either record as an invoice-item mapping table.
PayPal Fields Track Payment Status Not Inventory Items
The custom fields added to the AR Payment screen are PayPal Customer Email, PayPal Invoice ID, PayPal Invoice Status, PayPal Invoice Number, Transaction ID, PayPal Invoice URL, Refund Number, and PayPal Paid Amount. Each field supports payment delivery, status checks, or refund tracking.
The processing screen also displays Payment Ref, Customer, Customer Email, Currency and Amount, Sales Order, Invoice Number, PayPal Invoice Number, PayPal Status, and Transaction ID. None of the documented columns identifies an item, SKU, quantity, warehouse, item class, or product alias.
PayPal Invoice Status can be Sent, Partially Paid, Paid, Cancelled, Refunded, or Partially Refunded. These statuses govern the AR Payment lifecycle and do not validate invoice-line-to-item matching.
Validation Rules Apply to Payments and Requests
The guide documents validation and troubleshooting for PayPal credentials, customer email, invoice status, release eligibility, and refunds. Test Connection validates the API credentials on Payment Methods. A Customer Payment Method supplies the customer’s PayPal email address.
A payment must not have been sent previously before Send PayPal Request is used. A payment still in Sent status cannot be released because PayPal has not confirmed payment. Refunds require a Paid PayPal state and a fully released local payment. These are payment-level rules.
The source gives no item-mapping validator, line-error field, item exception log, or rule that blocks a PayPal request when an Acumatica invoice contains a particular item. It does not provide an item reconciliation screen after the request is sent.
Where to Check the Documented PayPal Data
The Biz-Tech Services PayPal Acumatica Integrator exposes payment and document evidence in the following documented screens and fields. None is identified as an item-mapping review.
1. On Sales Orders (SO301000), review the Payments tab and linked AR Payment
2. On Payments and Applications (AR302000), review PayPal Customer Email, PayPal Invoice ID, PayPal Invoice Number, PayPal Invoice URL, and PayPal Invoice Status
3. Review Orders to Apply and Documents to Apply for document-level applications
4. On the Check PayPal Payment Status processing screen, review Sales Order and Invoice Nbr links
5. Review Currency and Amount, PayPal Status, Transaction ID, and PayPal Paid Amount for payment reconciliation
6. Treat the absence of Inventory ID, SKU, quantity, item class, and alias fields as a documented scope boundary
PayPal Invoice Line Mapping Frequently Asked Questions
Does the PayPal integration map invoice lines to Inventory IDs?
The Biz-Tech Services Acumatica PayPal Integration guide does not document that capability. It describes totals, outstanding balances, payment applications, and PayPal status fields, but it names no Inventory ID or item-mapping field.
Does PayPal receive the sales order line items?
The source says the Sales Order workflow reads the order total, currency, and customer details. It does not say that individual order lines are sent.
What amount is used when the request starts from an AR invoice?
The PayPal invoice amount matches the outstanding balance on the AR invoice. No line allocation rule is supplied.
Can an item SKU be stored in the payment description?
The standalone payment accepts an optional description, but the guide does not define it as a SKU, item alias, or product-matching field.
Are ARAdjust and SOAdjust item mapping records?
The source says PayPal fields are available on ARAdjust and SOAdjust applied-to lines to keep status information consistent. It does not describe them as item cross-reference records.
Does the connector create missing Acumatica items from PayPal?
No item-creation workflow is documented. The customization creates and updates AR Payments and PayPal invoices, not inventory records.
Can item classes or aliases control PayPal invoice content?
The guide does not mention item classes, item aliases, alternate product IDs, or rules that use them to build a PayPal invoice.
Where should item mapping be validated?
The supplied PayPal documentation gives no item-mapping validation screen. Item accuracy must be established in the source Acumatica document or another documented product process before a PayPal request is created.
Work With Biz Tech Services on PayPal Payment Requests
The documented PayPal customization sends document-level payment requests and tracks their status through AR Payment fields and application records. It does not define product, SKU, item-class, alias, or line-level Inventory ID mapping.
If your team needs help confirming the boundary between Acumatica document data and PayPal payment requests, the Biz-Tech Services Acumatica PayPal Integrator can support your implementation. Visit https://biz-techservices.com to contact Biz-Tech Services or schedule a personalized demonstration.
Check the video lesson here: https://www.youtube.com/watch?v=wkjPKdLzv2M
