Legal Software

7 Checks Before a Filevine Bulk Billing Import

Before a Filevine billing import, check the operation, record identifiers, file structure, financial meaning, exceptions, recovery plan, and saved results. LOIS can validate a CSV, but your firm still has to decide whether those rows represent the change it actually wants.

Explore the full Tepconic guide:

Legal Software Implementation

→

Rows of graphite tiles pass through a gold gate while three silver tiles wait in a separate curved side channel.

A spreadsheet can pass a technical check and still describe the wrong business decision. For example, valid time entries may belong to the wrong project, or a corrected file may include work that was already imported. That is why approval needs more than a green status.

What does the new Filevine capability support?

Filevine’s November 4 release introduces CSV-based bulk operations for billing records, with validation before approval. The help guide updated November 10 limits access to account admins and describes supported records and file requirements. Check that current guide for your exact operation; this is not a general-purpose case-data migration tool.

The seven checks below are Tepconic’s implementation recommendations. They are not a vendor certification, accounting instructions, or permission to change financial records without your firm’s approval.

1. Are you clear about what will change?

Write a one-sentence change request before preparing the file. “Add missing time entries from the approved source for this period” is a different task from changing existing entries. Keep creation, correction, and deletion work separate so the reviewer can understand the intended result.

Name the preparer, business approver, and administrator who will execute the change. They may overlap in a small firm, but the responsibilities should remain clear. A person with technical access should not have to guess whether a billing decision has been approved.

2. Can every row be matched unambiguously?

Filevine’s guide calls for numeric project IDs in billing-entry files and supports external row identifiers for later matching. Use the current specification rather than substituting a client name or an identifier from another system.

Before approval, have someone trace a sample from the source to the intended Filevine project. Include clients with similar names and clients with multiple matters. This catches a class of mistake that a well-formed identifier alone cannot catch: a real record linked to the wrong real matter.

Keep a stable source-row identifier in your preparation records. It should let you answer, “Where did this come from, and have we handled it already?” without searching old email attachments.

3. Does the file follow the current specification?

The guide requires a CSV with headers and one record type per file. For billing entries, it says to supply rates rather than assume rate schedules will fill them in. Follow the documented columns; do not add spreadsheet totals or helper columns to the upload.

Keep your working spreadsheet separate from the final approved CSV. Formulas, comments, and lookup columns can help preparation, but they can also make the upload ambiguous. Give the final file a version and stop editing it once the approver has reviewed it. If the file changes, review the changed version.

4. Do the numbers mean what finance expects?

Ask the billing owner to review the actual business meaning of dates, quantities, rates, and classifications. A correct number in the wrong field is still wrong. For instance, a spreadsheet may store elapsed minutes while the intended entry represents hours. Do not fix that through an undocumented assumption at upload time.

Calculate expected row counts and relevant totals independently of the import screen. Separate totals by record type and operation. Compare a correction’s expected difference with the original position, rather than treating the new file’s sum as the whole story.

Your finance professionals should approve accounting treatment and any trust-related implications. This checklist helps organize the technical change; it does not replace their judgment.

5. What happens to rows that do not pass?

Filevine documents a choice between proceeding with passing rows or correcting the file and starting a new import. Decide who can make that choice before the administrator reaches it.

A partially completed batch can be appropriate, but only if someone owns the remainder. Keep an exception record that identifies each rejected source row, the reason, the decision, and whether a later correction was completed. Do not call a batch finished while its unresolved rows live only in someone’s inbox.

For a retry, use the actual saved results to determine what remains. Re-uploading the original file because “some of it failed” is not a reliable recovery method.

6. Have you planned recovery before approval?

The help guide warns that an import already underway cannot always be stopped and saved records remain. Do not treat the approval button as a reversible preview or promise your team a universal one-click undo.

Agree a vendor-supported test and recovery approach with the administrator before the live change. Preserve the approved source, the prior values needed for the chosen correction, and the result report. Ask Filevine Support about any unclear reversal behavior. Deleting newly created records is not the same as restoring every kind of financial change.

Start small enough that the billing owner can inspect every result. Use an approved testing arrangement; do not create fictional production transactions just to see what happens.

7. Can you prove the saved result matches the request?

Approval, execution, and reconciliation are separate checkpoints. After execution, compare the completed records with the approved file and the expected differences. Check relationships and representative values, not just the success message.

Reconcile relevant downstream reports or connected systems as a separate step. A saved Filevine entry does not, by itself, establish that another system has accepted it or that the firm’s financial reporting is correct. Record the remaining discrepancy and its owner rather than silently choosing whichever total looks convenient.

Tepconic judgment: the import needs a controlled change process

Filevine’s new capability reduces manual entry. Make’s October guidance on dependable agent execution emphasizes the surrounding systems, knowledge, and controls. Our synthesis is straightforward: faster execution makes the approval evidence and follow-through more important, not less.

For your first batch, keep the scope narrow and make the reviewer’s job easy: one defined change, one approved file, and an understandable reconciliation. Once that works, decide whether a recurring supported integration would be better than repeated uploads.

Our Filevine implementation guide explains how this fits the wider setup. Tepconic’s legal software implementation services cover data mapping, configuration, testing, and coordination with the people who own the process.

Frequently asked questions

Does LOIS validation replace billing approval?

No. Technical validation and business approval answer different questions. Your firm still needs to confirm the intended records, values, and financial treatment before execution.

Can we use this for every Filevine record type?

Do not assume so. The current release and help guide describe billing records. Verify the supported area and operation in the current vendor documentation before preparing a file.

Can Tepconic help prepare and test a Filevine import?

Yes. Tepconic can map source records, prepare the supported import structure, coordinate testing, and design reconciliation with your billing owner. Talk with Tepconic about your Filevine data change. Your firm retains approval of the financial decisions and execution authority.