Skip to main content

SharePoint 4 Biz - Setting up Expense/Purchase Register

Very often we need somewhere to register purchases or expenses. There can be various reasons for that, but the main are:
- store all expenses in one register to categorize, approve, review, report etc.
- ability to upload scanned receipts for future claims, reimbursements, warranties etc.

So here's how it can be done in SharePoint 2013 or SharePoint Online / Office 365.

Start with creating a content type - in our case it is Receipt:

1. Go to Site settings:


2. Select Site content types:

3. Click "Create":

4. Provide content type details. We suggest to create a new Group for it and inherit from Document content type:

5. Add site columns to the content type. We think the most important would be Purchase Category (Travel, Food, Activities etc.), Vendor, Amount, Purchase Date and Warranty Date:


Then we create a document library:

6. Go to Add an app:
 7. Select Document Library:

8. Provide a name (Receipts in our case):
 9. Go to Library Settings:


10. Go to Advanced settings, set Allow management of content types to Yes and click OK button:

11. Add the Receipt content type and delete the Document content type:


That's it - our new Receipts register is ready to use.

Now you could either scan your receipts or take a photo with your mobile phone and upload to this document library.

Comments

Popular posts from this blog

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

This post is a follow up on the issues that I have got setting up External Content Type (ECT) on SharePoint 2010 Foundation that was going to connect to remote SQL Server database for information. I cannot use my SharePoint user accounts to access SQL Server. According to the information I have discovered ECT and Business Connectivity Services are available in the SharePoint 2010 Foundation, but there are some issues if you want to use authentication methods in your external connections that are different from Windows Identity or Current User Identity. This is because there is no Secure Store Service in SharePoint 2010 Foundation which serves as an impersonation hub and is only available in SharePoint 2010 Server edition. The issues are coming from the fact that you can actually create ECT in SharePoint Designer 2010 providing just Secure Store ID and system would ask you for credentials and here you go, but when you try to use your ECT in External Lists or as a lookup columns you w...

SharePoint 2013 Development and Consulting - Laptop & Conferencing Experience with Lync

Have just jumped on a brand new SharePoint 2013 massive Intranet project and because of specific working conditions have found some items that required addressing almost immediately in order to continue the job. Maybe this will be interesting to someone else who is about to start SharePoint 2013 development to have an idea of what might be necessary. I started working with SharePoint using my own infrastructure in 2009. I used iMac with 320GB HDD and 4GB RAM running VMWare Fusion to virtualise Windows  environment ( SQL Server 2008, standalone SharePoint 2007, Visual Studio 2008, Office 2007). It was all-in-one virtual machine. A bit slow, but enough for any SharePoint work that I had at that time. For communication with colleagues and partners we used GoToMeeting . Great tool that worked (and still works) without any problems. Voice, video, screen-sharing - all worked well using built-in audio/video hardware. In 2010 I got a MacBook Pro  with 500GB HDD and 8GB ...

InfoPath 2013 Preview - URL not valid error when publishing

In InfoPath 2010 there is a problem when you try to publish a Form to a SharePoint site that doesn't have root site collection. You will get an error message "The following url is not valid". It's described here:   http://support.microsoft.com/kb/981854 The solution is to create root site collection for the Web application. Same problem is with InfoPath 2013: In my situation I didn't create the root site collection initially, but used "/sites" managed path instead for all site collections. To solve the problem with InfoPath I had to create it. Used a new site template "Project Site". Will get a chance to research that too. :)