Resolved Issues

• Bullhorn:
  • Fixed an issue where a leading space threw an error when creating a Bilflo contractor.
  • Fixed an issue where “District of Columbia” was not interpreted as a Bilflo state.
  • Updated the termination action to include a new status based on a customer request.
• Contract Jobs:
  • Fixed an issue where an error occurred when creating/updating a contract job with the salary timecard.
• Performance:
  • Fixed a connection pool exhaustion issue that caused occasional unhandled exceptions during peak traffic. Implemented better resource cleanup and enhanced database access efficiency.

Resolved Issues

• Professional Services:
  • Added a new feature to a custom report, as requested.
  • Updated the stored procedure to pull various custom reports, as requested.

Resolved Issues

• Professional Service:
  • Various updates to a custom report regarding updated logic, as requested.

Resolved Issues

• Bullhorn:
  • Fixed an issue where the Bullhorn EndDate was not interpreted accurately when terminating the associated Bilflo contract job.
• Direct Hires:
  • Fixed an issue where the Payment Term was not populating the database accurately when creating a direct hire job or direct hire invoice.
• Professional Service:
  • Updated the contract overview page slideout modal based on a customer request.
• Workflow:
  • Fixed an issue where the client contact denied functionality did not trigger a notification email due to the workflow configuration.

Resolved Issues

• Bullhorn:
  • Fixed an issue where the Bullhorn candidate “Social Security Number” field was not passed through when creating a Bilflo contractor record.
• Expenses:
  • Fixed an issue where the IsCostRateLocked was set to true, and the CostRate AND CostQuantity fields were set to read-only.

New Feature!

• Professional Service:
  • Released a new feature that notifies a team member (or any email recipient) if any timecards have been approved or denied in Bilflo, as well as additional information about who updated the timecard, and information about the job, client, etc.
    • NOTE: This feature can be configured to include various aspects of the contractor, timecard, job, client, etc., and currently sends an email when a specific event occurs (e.g., when a timecard is updated to the “approved” or “denied” status).
    • See below for examples of the approved/denied notification emails:

Resolved Issues

• API:
  • Fixed an issue where the social security number did not get inserted when sent via the Bullhorn integration or when sent via the Bilflo API.
• QuickBooks:
  • Fixed an issue where class mappings were not accurate if multiple line items on an invoice were associated with different custom fields.

Resolved Issues

• API:
  • Fixed an issue on the Bilflo API where an error message was displayed.
• Bullhorn:
  • Fixed an issue where the Bullhorn custom field values did not return the correct value for “Don’t Bill Expenses to the Client” and “Don’t Bill Per Diem to the Client”.
• Burden:
  • Fixed an issue where some timecards had transactions with calculated burdens, but the UI showed 0.00% for the burden.
• Direct Hires:
  • Fixed an issue where the direct hire page shows an outstanding “Balance” on the Payments section when the total invoice amount matches the payment amount.
  • Fixed an issue where the direct hire invoices section did not populate the payment term in the database, causing an error when exporting to QuickBooks.
• Professional Services:
  • Updated custom report based on customer requests (e.g., CSV file name, logic definitions, etc.)
  • Fixed an issue where a custom report displayed a duplicate record when expenses were included on the timecard, and the sort order was incorrect.
  • Updated custom report based on customer requests (e.g., display specific expense item name, quantity, and rate if an expense is included on the timecard)

Resolved Issues

• API:
  • Fixed an issue where a 502 Bad Gateway error occurred on various endpoints.
• Bullhorn:
  • Fixed an issue where the Bullhorn custom field “categories” did not come over to Bilflo accurately due to a JSON value returned from Bullhorn.
  • Fixed an issue where Bullhorn updated the Burden Manual values on a Bilflo job when the company used worker comp codes to calculate the total burden.
  • Fixed an issue where the Bullhorn placement was not updating PBI rates on the job if the employee type was 1099.
• Contract Jobs:
  • Fixed an issue where Burdens on the job were not being saved.
  • Fixed an issue where an error was displayed when opening a terminated job.
• Direct Hires:
  • Fixed an issue where the applied payment displayed an inaccurate balance in the “Payments” section.
  • Fixed an issue where an error was displayed when saving due to a rounding error on the back end (e.g., 10.0001 displayed as 10 and throwing an error because the values did not match).
• Reports:
  • Fixed an issue related to various professional service reports as requested.

New Feature!

• Sage Intacct:
  • Bilflo can now sync Bilflo clients to create Sage Intacct customers and export Bilflo invoices to create Sage Intacct invoices.
  • If the customer has already been created in Sage Intacct, admins can map Bilflo clients to Sage Intacct customers. If the customer has not been created in Sage Intacct yet, admins can go to the Billing > Accounting > Sync page to prompt the action to sync (or create/update) the customer record.
  • Prior to exporting invoices (on the Billing > Accounting > Export page), admins can map Bilflo PBIs to Sage Intacct GL Accounts so the invoice line items are generated correctly based on the requirements for Sage Intacct.

New Feature!

• Specify expenses on a contract job:
  • See here for an overview: https://www.loom.com/share/1c0343dc1bdf445f9293a242c6d3367d
• Enable Expenses:
  • Unchecked: Contractors cannot enter expenses on their timecards.
  • Checked: Contractors can enter expenses on their timecards.
  • This setting allows admins to control whether or not contractors can add expenses.
  • If no specific expense items are added using the “+ Add Expense Item” option, contractors will see the full list of expense items from the Global Lists page. If items are specified directly on the job, the contractor’s dropdown will only display those job-specific items.
• Approve Method:
  • Always select “Online”
    • (Note: This field will be removed from the front end soon to simplify setup and approval.)
• Don’t Bill Expenses to the Client:
  • Unchecked:
    • Expenses will be added to the invoice.
    • On the Contract Overview page, “Bill Quantity for Expenses” = 1.
  • Checked:
    • Expenses will not be added to the invoice.
    • On the Contract Overview page, “Bill Quantity for Expenses” = 0.
• Add Expense Items:
  • By default (to preserve existing functionality), if no expense items are added to the job, contractors will have access to all expense types listed on the Global Lists page.
  • If you add an expense item, only those selected will be available to the contractor for that job.
• Default Rates:
  • Admins can define a default Cost Rate and/or Bill Rate for each expense item on the Global Lists page.
  • If a default rate is set to $0.00, the rate entered on the timecard (i.e., Cost Rate) will be used as the base to calculate the alternate rate (i.e., Bill Rate).
  • If default rates are defined, those values will be automatically applied.

• Lock Cost Rate:
  • The lock icon next to an expense item allows admins to make the Rate field read-only for contractors.
    • Example: Contractors cannot edit the cost rate of $0.70 for “Mileage”.

• Max Limits:
  • Admins can enforce maximum subtotal limits for expense items. These limits can be based on:
    • Daily totals
    • Weekly totals
    • Monthly totals
  • Limits can be applied to either the Cost Subtotal, Bill Subtotal, or both independently.
  • Example: For “Mileage”:
    • Cost subtotal max: $100.00
    • Bill subtotal max: $200.00