Reconciliation file-UI fields mapping
The reconciliation file contains such fields.
- Please check the screenshots on where these values are fetched from ,on the platform.
Field Name |
Mapping to portal UI |
Invoice number |
AppXite Platform generated number per invoice receiver. |
Invoice Status |
Invoice state. Three possible statuses: New, Verified, Processed. |
Invoice date |
Billing cycle i.e. date when invoices are generated. |
Invoice provider |
Entity issuing the invoice. Visible under main reseller profile under Select organizations. |
Invoice receiver |
Entity receiving the invoice. 2. reseller on Distributor platform. |
Receiver status |
Invoice receiver status in the platform. Three possible statuses: New, Active, Blocked. |
Receiver ERP ID |
Field available to enter customer ERP ID for invoice receiver in AppXite platform. Can be used for data mapping purposes. |
Receiver country |
Country of invoice receiver as defined for the organization under legal details. |
Receiver VAT number |
VAT number of invoice receiver as defined for the organization under legal details. |
Contract number |
Field available to enter Contract number under Contract section in the Platform. Can be used for data mapping purposes. |
Contract reference number |
Field available to enter Contract reference number under Contract section in the Platform. Can be used for data mapping purposes. |
Reference contact person |
Field available to enter Reference contact person under Contract section in the Platform. |
Billing address |
Invoice receiver billing address as defined for the organization under billing address. Important to maintain this field up to date as this field is used to issue invoices. |
Account manager |
Account manager as defined for the organization under Contacts. |
Account manager email |
Account manager e-mail as defined for the organization under Contacts. |
Comments |
If the subscription was purchased outside of AppXite Platform but is synced from Vendor, this subscription will get a message "Created Automatically while synchronized", otherwise this field will be empty. |
Reseller name |
Entity part of the supply chain that is issuing the invoice to the end- customer. |
Customer name |
Entity that receives the final invoice. |
Offer name |
Offer name as available in the product catalog. |
Subscription name |
Purchased offer name. |
Subscription start date |
Start date of subscription. ![]() |
Subscription end date |
End date of subscription. |
Charge start date |
Start date for charge calculation in this billing period. |
Charge end date |
End date for charge calculation in this billing period. |
Charge type |
Charge Type. As possible statuses: Cycle Fee, Purchase Fee, Usage Fee, Correction, One-Time. |
Currency |
Invoicing currency. |
Customer Unit price |
Unit price for a subscription for outgoing invoice to invoice receiver. |
Customer quantity |
Quantity for subscription for outgoing invoice to invoice receiver. |
Customer total price |
Total price for a subscription for outgoing invoice to invoice receiver. |
Vendor |
Vendor providing particular offer. |
Reseller Unit Price |
Unit price for a subscription for incoming invoice to invoice provider. As a Disti , reseller unit price means in price for the distributor. As a reseller, reseller price is my unit price. |
Reseller Total Price |
Quantity for subscription for incoming invoice to invoice provider. As a Disti , reseller unit price means in price for the distributor. As a reseller, reseller price is my unit price. |
Reseller Currency |
Total price for a subscription for incoming invoice to invoice provider. As a difference between Customer Price and Reseller Price can be calculated profitability of subscription, per customer, per reseller, or per vendor. |
Support Currency |
Currency for Support Contract that can be used either for Channel Rebates management or additional fee for service provided that is linked to invoice amount. |
Support Total Price |
Total amount calculated in set currency for Support Contract and invoiced to invoice receiver. |
Retail Price Source |
Based on which price calculation is done: Vendor Retail Price or Reseller In Price |
Retail Price Markup |
The mark-up on retail price. |
Customer Markup |
Customer-specific markup |
Price Markup Start Date |
Date from which mark-up is effective. |
Invoice Provider Id |
AppXite Platform generated GUID number for Invoice Provider. |
Invoice Receiver Id |
AppXite Platform generated GUID number for Invoice Receiver |
Reseller Id |
AppXite Platform generated GUID number for Reseller |
Customer Id |
AppXite Platform generated GUID number for Customer (consuming the subscription) |
Offer Id |
AppXite Platform generated GUID number for Offer |
Vendor Offer Id |
Vendor generated GUID number for Offer (For every other vendor except Microsoft) Vendor Offer ID is the same as Offer ID generated by Platform |
Subscription Id |
Platform generated GUID number for provisioned Offer i.e. subscription |
Vendor Subscription Id |
Vendor generated GUID number for provisioned Offer i.e. subscription. For example for Microsoft this corresponds to SyndicationPartnerSubscriptionNumber. |
Custom offer properties |
Information regarding custom offer properties created via API |
Buyer Purchase Order Number |
Buyer Purchase Order number. |
Seller Purchase Order Number |
Seller Purchase Order number (under construction on the platform)
|
Invoice Reference # |
Unique invoice reference number across vendors and sellers |
Was this article helpful?
Articles in this section
- Invoicing by contract
- How can I see details of my incoming invoice?
- What will I see in outgoing invoices?
- How can I see details of my outgoing invoice?
- How can I see outgoing invoices in customer view?
- Incoming invoices in customer view vs. outgoing invoices in seller view
- How to get full reconciliation data?
- Reconciliation file-UI fields mapping
- Storing tax invoices on the platform
Add comment
Please sign in to leave a comment.