# January 12th - New features & Bugfixes

## :tada: New Features

### Added surcharge calculations dynamically in invoice 

Now, invoices surcharge calculations are being calculated dynamically on the fly rather than pre-calculated. 

### Added Payroc payment link in order details screen

Now, in the order details screen, in the payments section, a new button is added to handle payments through Payroc.

### Payroc for payment in platform

{% embed url="<https://www.loom.com/share/51a9e82c868d413e861c5caee51aa98f>" %}

Now, in the platform payment workflow, we are using Payroc as payment provider.

### Added new placement type

Now, a new placement type was added to the platform: Foil.

### New file storage system

{% embed url="<https://www.loom.com/share/5449f132565b4cfea93b53ab55d2c2cc>" %}

Now, a new file storage system stores files in the cloud (AWS S3 Bucket) rather than Apache server. This new file storage also has a tagging feature for categorization and an “email order” feature to specify the order in which the files are collated and sent for specific clients

### Email Automation&#xD;

This automation ensures that specific client(s) receive the documents they require in the order they want to receive them in.

When the automated final invoice emails are sent, the selected files in the file storage will be converted to PDF, combined into one PDF, and attached to the emails sent to specific client(s).

Note: This newly released feature is partially rolled out and will only work for certain specified clients, but can be expanded to work for other clients in the future.

### Quickbooks Bilateral Sync (First Phase)

\
Added the ability to retrieve invoice and payment information from Quickbooks Online.

## &#x20;:lady\_beetle: Bugfixes

:heavy\_check\_mark:  Fixed issue with card payments receipt emails.

:heavy\_check\_mark:  Fixed issue with saved cards in Payroc.

:heavy\_check\_mark:  Fixed shipped units count in the daily report.

:heavy\_check\_mark:  Fixed final invoice emails not being sent.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.culturestudio.com/release-notes/decorator-platform/january-12th-new-features-and-bugfixes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.