Payments: Image vs Attachements?

1

Recently moved to Cloud version and caught up many versions.

On Payment there is now both an IMAGE field (from entry form) and an attachment button (from view).

What is the intent of the two and how are people using this? i.e. Image for copy of check or ACH confimation etc. and attachment for copies of the thing being paid (invoice/insurance policy, etc.).

Thanks

2

The image and attachment are both used to achieve more or less the same result, however, there are the following differences:

  1. Obviously, Attachments accept all types of files: images, videos, spreadsheets and zipped folder among others, while Image field accept image files only.

  2. Attachments can hold virtually unlimited number of files. The Image field can hold One file only.

  3. Images are available in Edit forms and can be used for quick entry by owners who can, for example, enter a blank Expense Claim from their mobile device, take a quick camera shot of the image and share the link with the accountant to complete the processing. This can also be used alongside Extensions to achieve an automated data entry using AI and OCR.

  4. Attachments are viewable on View screens only while Images are viewable both on Edit screen and tab view as well like below, but not on View screen – I wonder why!

    Screenshot_20260303_003548
    Screenshot_20260303_0035482279×977 204 KB

  5. Images are stored within the object while attachments aren’t. This makes them an integral part of the accounting record and also enable easy access for developers as explained in point #3

3

Thanks. I followed that. Really, was trying to understand intent and use, not technical distinction. For example.

One Could use the image as the image of a cheque and the attachement as the image of the thing being paid by the check. For Fixed Assets - image as a picture of the asset, attachments for related documents (maintenance contracts etc.) Just wondered wat users are doing. If I have a sales invoice that was created by an external system, I’d use image as it is am image of the document. Attachments for supporting documents (client timesheets etc.)

Sounds like no particular ‘intent’ from a development perspective. Was just curious what folks SOP’s were for the two.

Thanks.