Publisher Compensation Statements FAQs

Publisher Compensation Statements FAQs

What are Pub Comp Statement files?

Pub Comp statements are Excel reports that show all content invoiced in a calendar month in which compensation is owed to the publisher.

How frequently are Pub Comp statements sent?

Pub Comp statements are sent monthly, typically in the first week of the following month, e.g., orders invoiced in November will be sent in early December.

Who are Pub Comp statements sent to? How do I update who they are sent to?

Pub Comp statements are sent to all email addresses associated with the Publisher’s Oracle Supplier account.

If an email address needs to be added or removed, please contact your Customer Success Manager or email Pub.AP@vitalsource.com.

Why are there separate statements for BNED?

At the beginning of BNED’s relationship with VST, Customer Success requested BNED sales be displayed in a separate Pub Comp statement due to varying publisher payment terms.

Where do I send questions about my statement?

Questions can be sent to Pub.AP@vitalsource.com.

How do I read the Pub Comp file?

Please reference the table below which contains the column, column header, and definition in the Pub Comp excel file.

Column Header Definition
VST REFERENCE NUMBER Internal VST invoice number
TRANSACTION_DATE Date on which billable code was created or redeemed (dependent upon billing trigger)
TRANSACTION_TYPE VST internal transaction classification
TRANSACTION_TYPE_CLASSIFICATION Simplified classification of transaction types into four categories: Barnes IA. Barnes Non IA, IA and All Other Types to support easier reporting
TRANSACTION Sale or refund
BILLING_MODEL Defines how VST is transacting on the individual title.
RINGGOLD_ID Industry wide ID assigned to each school by https://www.ringgold.org/. IMPORTANT: This will NOT be filled in for VST ecommerce sales. These ID’s will be filled in as they are populated by VST
IPEDS_ID Industry wide ID assigned to each school by https://nces.ed.gov/ipeds/. IMPORTANT: This will NOT be filled in for VST ecommerce sales. These ID’s will be filled in as they are populated by VST
VST_DIST_ID Internal VST ID for each Distributor
DISTRIBUTOR Name of account who has created/redeemed code
API Manage 'System User' who created/redeemed the code; field will only be populated if API was used to create/redeem code
INSTITUTION_NAME Store Purchase = Populated with institution name selected by Bookshelf user upon account creation (not currently required); Non-store purchase = blank
ADDRESS Store Purchase = blank; Non-store purchase = Distributor's address
STATE or PROVINCE Store Purchase = blank; Non-store purchase = Distributor's state or province
POSTAL_CODE Store Purchase = Populated with Bookshelf user's postal code; Non-store purchase = Distributor's postal code
COUNTRY Store Purchase = Populated with Bookshelf user's Country if provided; Non-store purchase = Distributor's Country
Child Company State If Distributor is a child of a parent account, this is the US state the child company is based in
PUBLISHER Content owner/publisher name
REDISTRIBUTOR If content owner/publisher grants access to another account to "Redistribute" their content, the account name granted access will be listed as "Redistributor"
PRODUCT_TYPE Identifies whether line is for package SKU, package component, or single.
PACKAGE_SKU If order line is for a package, the package SKU will be displayed; otherwise blank for non-package orders
SKU SKU in which code was created/redeemed against. This column WILL include package components. If SKU includes "R" that indicates a rental duration was sold.
VBID VBID associated to the "SKU"
EISBN eISBN value of VBID/SKU
CUSTOM_ISBN Custom ISBN/LSI ID listed in Manage; specific to a content owner and distributor
IA_CPID Custom ISBN associated to their Inclusive Access program in Verba Connect
CONNECT_ISBN ISBN/SKU listed in Connect for product. This may be the same as ISBN/SKU in Manage or could vary
TITLE Title for VBID listed in Manage
AUTHOR Author for VBID listed in Manage
CONTENT_TYPE Value listed in "Kind" metadata field on asset in Manage (i.e. Book, Online Resource, etc.)
DURATION_DAYS Rentals = # of days for license; Perpetual and Verba = blank;
DISCOUNT_CODE Displays discount code (when applicable) used to calculate pub comp
CODE_TAG If code is tagged upon creation, value will be passed and displayed here; otherwise blank
TERM_NAME Enrollment billing = will be populated with term name submitted by CS; otherwise it will display the Year & Month of order date
TRANSACTED_PRICE_TYPE Indicates what "Price Type" in VitalSource systems applies to the transaction
QUANTITY Quantity of sale or refund per transaction line
TRANSACTED_UNIT_PRICE Distributor's price per unit
TRANSACTED_PRICE_TOTAL Distributor's total price invoiced or refunded (TRANSACTED_PRICE x QUANTITY); When package price exists, Package Component lines will be 0.00 and all details will be found on main Package SKU line (Column T = PACKAGE)
TRANSACTED_PRICE_CURRENCY Currency in which the Distributor transacts
TRANSACTION_FEE Fee charged to applicable publishers for ecommerce sales, which covers fees charged by 3rd party payment services
PUB_COMP_UNIT Pub comp amount per unit
CA_GST Goods and services tax (Canada) - No longer applicable
PUB_COMP_TOTAL Total pub comp paid (PUB_COMP_UNIT$ x QUANTITY)
PUB_COMP_CURRENCY Currency in which content owner/publisher is paid
EFFECTIVE_DISCOUNT Final discount VST receives. Formula = 1 - (PUB_COMP_TOTAL/TRANSACTED_PRICE_TOTAL); Can appear as a larger or smaller discount than expected when conversion rates are applied
EXCHANGE_RATE Exchange rate used when Distributor currency varies from content owner/pub currency (If not exchange needed, value = 1)
VST_MARGIN_USD VST's margin in USD after pub comp has been paid
PUB_COMP_DUE_DATE Date in which pub comp is due to be paid
CAMPUS_ID Campus identifier associated with the adoption in Verba Connect (Effective on NOV-25 statements)
Was this article helpful?