Before you begin
- A reviewed invoice and the recipient's required format and agreed billing identifiers.
What to do
- Open the invoice in Billing and inspect its matter, client, timekeepers, line descriptions and amounts. Resolve invoice errors before exporting. A successful file download will reproduce the selected invoice; it does not review the firm's billing agreement.
- Check the recipient's required LEDES version and billing identifiers against the export choices shown. Use the export that matches the requirement. If a requested version is unavailable, confirm another acceptable format with the recipient before preparing the submission.
- Review the export's restrictions and any requested details. Use the identifiers and classifications the client approved. Do not infer a timekeeper classification from a job title or alter a recorded amount merely to satisfy a file format.
- Run the export and read any refusal. A format may reject a value it cannot represent, including a fractional-cent amount. Resolve the underlying invoice or format issue through the firm's billing process, then create and inspect a fresh export.
- Open or validate the downloaded file through the firm's normal billing process before uploading it to the recipient's system. Keep that system's acceptance or rejection separately. If BRON's export fails, check the visible message and retry only after addressing the stated issue.
What you should see
You have an inspected LEDES file in a supported format and can submit it through the firm's existing process while tracking the recipient's outcome separately.
Limits and unresolved problems
LEDES support is export only. BRON does not submit the file to an e-billing vendor, and download success is not vendor acceptance, client approval or payment. Format restrictions remain specific to the selected export.
Product scope and requirements
Related guides
Still need a hand?
Record the screen, time, displayed status and steps you tried. Use your signed-in support route or contact your firm administrator. Do not include credentials or confidential documents in a public message.
Support contacts