New Features!

See General Overview Here – https://www.loom.com/share/448be8ab05034367b6a45d43fe209092

Bilflo is pleased to announce the release of Bilflo 4.0, featuring an exciting new addition – Invoice Frequency. As part of our commitment to constant improvement, we have enhanced and upgraded our Invoicing feature to better meet your needs. This proves the dedication to delivering top-notch solutions that will help the users cater to varying invoice ranges, and Bilflo 4.0 is just another step in that direction.

• What is Invoice Frequency? 
  • This feature provides users with various options to allow invoices to be generated using various date ranges and grouping options. Customers on the Enterprise plan will have the flexibility to invoice on a daily, weekly, bi-weekly, semi-monthly, or monthly basis, whereas customers on the Pro plan will have the flexibility to invoice on a weekly basis. 
• How will it affect my current invoicing workflow? Can I still invoice the same way?
  • Our team has carefully considered not only enhancements but also the ease of transitions from one upgrade to another. We understand the importance of seamless transitions and have put great emphasis on ensuring a smooth experience when moving from one upgrade to the next.
    • Your current invoice settings will be carried over so existing invoice groups should still function the same: (i.e. remittance, payment terms, email recipients, format, etc.)
    • The Invoice Frequency default is set to “weekly classic” which mirrors the frequency used before this feature was released. 
    • The Invoice Columns will be the same in this format/order:
      • Timecard Period
      • Contractor Name
      • Job Title
      • Pay Bill Item 
      • Bill Quantity 
      • Bill Rate

Resolved Issues

• Bullhorn:
  • Fixed an issue due to the Bullhorn Address Display Name exceeding character limits.
• Contractor:
  • Fixed an issue where clicking Save on the Contractor profile resulted in an error.
• Invoices:
  • Fixed an issue where invoice quantities and rates were displaying inaccurate values for API timecards.
  • Fixed an issue where Direct Labor calculations were calculated incorrectly when editing a line item or adding a line item to an invoice.

Resolved Issues

• Bilflo API:
  • Updated the database to capture payload information for troubleshooting purposes.
• Burdens:
  • Removed the ability to create a Burden rate using a flat rate value. Users can still create burden rates using a percentage value.
• Contract Starts:
  • Fixed an issue where the graph showed duplicate date values due to varying week ending dates on the timecards.
• Invoicing:
  • Fixed an issue where future timecard records were not included on the Invoice Preview but were still included on the invoice and invoice PDF when created.
  • Fixed an issue where the allocation section on the daily third party timecard was not included on the timecard attached to the invoice PDF.
• Metrics:
  • Fixed an issue where a Combined GP metric was displaying different results when logged in a team member.
• Scheduled Emails:
  • Fixed an issue where the Email column showed an inaccurate email address (it showed the Sender value only on the UI) but the email was successfully delivered to the expected recipient.
• Timecard detail page:
  • Fixed an issue where the timestamps were using the server’s timezone on the timecard detail page as well as the timecard attached to the invoice PDF.
• Timecard Report:
  • Fixed an issue where the table did not update the UI after deleting/adding/updating timecards until the webpage was refreshed.

Resolved Issues

• Bilflo API:
  • Updated the API to correct a 500 error that occurred when passing through an AddressId.
• Client Address:
  • Fixed an issue where an error occurred when deleting a client address.
• Client Contact:
  • Fixed an issue where an error occurred when deleting a client contact.
• Contract Jobs:
  • Updated the default values for the file upload and file requirement to false on the contract detail page.
• Timecards:
  • Fixed an issue where a UI error occurred on the daily third party timecard.
  • Fixed an issue where the Holiday transaction text was duplicated on the outstanding timecards page for contractors.
  • Fixed an issue where a timecard with CA (over 8/40) overtime rules was not calculating hours properly.
  • Fixed an issue where an error occurred for detailed clock-in clock-out timecards with overnight calculations.

Resolved Issues

• Bilflo API:
  • Various updates to the Bilflo API related to placements coming into Bilflo, authorization records, etc.
• Bilflo Query Engine:
  • Added a new database feature that will continue to be updated and expanded to end users at a later time.
• Bulk Time Import:
  • Various updates to the Bulk Time Import feature.
• PrismHR:
  • Fixed an issue where the contract overview page did not display records when showing jobs with PrismHR custom fields.
• Server Authentication:
  • Fixed an issue where an error occurred due to an expired server authorization token.

New Features! See here for an overview – https://www.loom.com/share/449e89e7d1214ae8ae5e873479947ee5

• New Timecard: “Daily Third Party”
  • On the contract job, we added a new time collection method called “Daily Third Party”. This allows the user to allocate totals to specific items on each day worked.
  • There is also a new field (specific to this timecard type) called “Timecard Dependency”, which allows you to select which timecard the contractor is going to use to enter their daily time:
    • Clock-in Clock-out
    • Daily Timecard (daily totals)
    • Detailed Clock-in Clock-out (overnight)
• PBI Attribute: “Use Quantities as Hours”
  • Under Settings > Pay Bill Items, when you select a specific item (e.g. Regular Time) there is a new attribute that allows the user to allocate time worked to these items.
• Ability to manage file upload section on the timecard page: Allow and/or Require
  • Currently on timecards, if an expense is included on the timecard, there is a section where users can upload documents to the timecard.
  • Now, that option can be managed from the contract job page to either allow files to be uploaded to timecards and also manage the option to require them.
  • On a related note, on the Invoice Settings page, there is an option to include documents on the invoice PDF and/or include an attached timecard to the invoice PDF.
    • Files uploaded for expenses and files uploaded with the Bulk timecard will always be displayed on the invoice PDF.
    • Outside of this, files will be included on the PDF if the job has “Allow Doc Upload” = true and if the invoice settings are set to include files on the invoice PDF.

Resolved Issues

• Blackout Dates:
  • Fixed an issue where the Blackout Dates feature (Settings > Global Lists > Blackout Dates) did not prevent users from entering time on specified dates.
• Contractors page:
  • Fixed an issue where custom fields were not displayed on the Contractors page (People > Contractors > click Columns) or on the CSV download (Actions > Download as CSV).

Resolved Issues

• Blackout:
  • Fixed an issue where clients were not listed in alphabetical order in the dropdown menu when creating a client-specific blackout date (i.e. date that prevents contractors from entering time on their clock-in clock-out, detailed clock-in clock-out, or daily timecards).
• Holiday:
  • Fixed an issue where an edge case did not calculate Holiday hours when contractors entered time on a holiday date (note: this only applies to clock-in clock-out, detailed clock-in clock-out, or daily timecards).
• Reports:
  • Fixed an issue where the Work Comp Code was calculated incorrectly (specifically the Work Comp Premium).
• QuickBooks Online (Payroll):
  • Removed an incomplete integration from production that our developers are currently working on in our test environments.

Resolved Issues

• Export:
  • Fixed an issue where the Sync page displayed records that were already marked as synced and the Export page displayed records that were already marked as exported.
• Invoices:
  • Fixed an issue where invoice PDFs contained image files that had conflicting aspect ratios.
• Permissions:
  • Fixed an issue where data access was not aligning with the team member permissions that were defined on the profile.
• QuickBooks Online:
  • Fixed an issue where the invoices that were exported to QuickBooks Online did not contain class mappings defined on the invoice mapping page.
• Reports:
  • Fixed an issue where various reports did not include records with $0 Sales and negative GP values.

Resolved Issues

• Approvers:
  • Fixed an issue where the Approval History page did not display timecard records prior to 3 months.
• Bilflo API:
  • Miscellaneous update to the Bilflo API.
• Bulk Time Import:
  • Fixed various errors when creating a bulk import template and when importing time.
• Bullhorn:
  • Fixed an issue where the user was redirected to the Integrations page when Authenticating the Bullhorn connection on the configuration page.
• Client Mapping:
  • Fixed an issue where the QuickBooks Online mapping pages displayed QuickBooks Desktop.
• Export Page:
  • Fixed an issue where the Export page displayed team member timecards even after being marked as exported.
• Invoice Settings:
  • Fixed an issue where the Service Offering Settings on the Invoice Settings page did not accurately reflect the results on the invoice PDFs.
  • Updated the Service Offering Settings page to add an option to include the invoice message on the export to the integrated accounting system.

New Feature!

• Integration Platform:
  • The Bilflo Team has updated our Open APIs and streamlined the communication between our system and any other applications that we’re integrating with to send/receive data.
  • This update also allows other applications to integrate with Bilflo (and allows Bilflo to integrate with future integration partners) more easily and in a more efficient way.
• Affected Areas:
  • Billing > Accounting > Sync and Export pages
    • Records that are sent to any of our integrations now have an updated status column to identify a clearer understanding of the errors that are received from the integration partner.
  • Settings > Integrations
    • Many of the changes that took place are noticeable on the back end of our development and allow our teams to get a clearer understanding of the records that are coming over as well as the information associated with those records (i.e. IDs, data logs, webhooks, etc.)