Skip to main content

How do I post a VSP payment in Barti?

VSP payments in mass payments: enter the payment in the right column and a CO-45 write-off in the middle column. For chargebacks, enter the negative amount in the right column and add two adjustment lines: one contractual write-off and one chargeback.

D
Written by Dan Healey

Who this is for: All Barti users who post VSP payments.

Before you start, you'll need:

  • The VSP EOB pulled from the VSP provider portal

  • The mass payment record open in Barti with header fields completed

See How do I post an insurance payment in Barti using mass payments? if you haven't set up the mass payment yet.


Key facts about VSP before you post

  • VSP has no payer ID. Type "VSP" directly in the payer field — it will not appear in the autocomplete dropdown.

  • VSP shows chargebacks as negative numbers in the payment column — there is no separate chargeback column.

  • VSP codes on their EOB often don't match CPT codes exactly. The first digits usually match; minor differences at the end are normal. Match by charge amount if a code is slightly off.

  • VSP claims must be manually updated in Barti after filing through the portal — they do not auto-update like TriZetto claims.

  • Always use Finalize, not Submit for VSP claims. Submit routes to TriZetto only.


Posting a standard VSP payment (positive amount)

Example: VSP pays $52.40 on an exam with a $170 billed charge.

  1. Enter $52.40 in the right column (Insurance Amount Paid).

  2. Calculate the write-off: $170 − $52.40 = $117.60.

  3. Click Add Adjustment and enter CO-45 (Contractual) with $117.60.

  4. Verify patient responsibility and insurance columns are zero.

  5. Click Apply Payment to Invoice.


Posting a VSP chargeback (negative amount)

Example: VSP shows −$95 for a progressive lens (the plan is charging you for lab material).

  1. Enter −$95 in the right column (Insurance Amount Paid).

  2. In the middle column, add two separate adjustment lines:

    • Line 1 — CO-45 Contractual: the full outstanding insurance balance (e.g., $140)

    • Line 2 — Chargeback: $95 (matching the negative payment amount)

  3. Verify the invoice zeros out.

  4. Click Apply Payment to Invoice.

Important: Never add the negative sign to the write-off in the middle column. The write-off is always a positive number. Only the Insurance Amount Paid column (right) carries the negative sign.

Why two lines instead of one? You could combine both into a single write-off ($235 in this example), but two separate lines are easier to audit and review later. Two lines is the recommended approach.


Handling multi-line and partial VSP EOBs

  • VSP sometimes splits one lens type into multiple lines (e.g., "Progressive Plastic 1" and "Progressive Plastic 2"). Add all payments for the same item together and post as one number.

  • If an item appears on the EOB but not on your invoice (e.g., digital aspheric), do not create an extra write-off for it — that creates an overpayment.

  • If an item is billed but does not appear on the EOB at all, write it off with a contractual adjustment. It was charged but the insurance is not addressing it.


Posting math quick reference

Scenario

Right column

Middle column

Standard payment ($52.40 on $170 charge)

$52.40

CO-45: $117.60

Chargeback only (−$95, insurance balance $140)

−$95

CO-45: $140 + Chargeback: $95


Troubleshooting

VSP isn't appearing in the payer dropdown.

VSP has no payer ID. Type "VSP" directly in the field and proceed — it will post correctly.

The invoice isn't zeroing out after I apply the payment.

Double-check that your middle column write-off and right column payment together account for the full outstanding insurance balance. A common mistake is forgetting to add the chargeback line when posting a negative amount.

The VSP code on the EOB doesn't match the CPT code on my invoice.

This is expected. VSP uses its own code structure that rarely maps 1:1 to standard CPT codes. Match line items by charge amount rather than expecting an exact code match.


Related articles

Did this answer your question?